Organizations often fail to move from ideas to action because they rely on top-down communication and assume that sharing information leads to behavior change. This episode emphasizes that understanding and behavior are separate stages, requiring intentional, participatory design. Effective change involves creating a narrative arc—building tension, explaining the "why," and guiding users through a system of feedback and reinforcement. Key to success is clarity around roles, timelines, and responsibilities, which prevents confusion and resistance. The creators of change—like brand designers—often excel at crafting assets but lack experience in engaging people. To overcome this, change initiatives must prioritize low-friction activation, such as simple, "ugly" drafts that encourage quick, scrappy contributions. These processes build trust and reduce the mental load on participants. Ultimately, change is not about broadcasting a message but about designing a shared journey that includes people at every stage, from tension to action. This approach transforms change from a source of friction into a manageable, human-centered process.
If you are an expert brand designer and you go off into your brand cave and you come back
bringing the tablets of the new brand, that's all within your expertise as a professional.
But the service design of bringing people along to contribute to that is probably not what you
went to school for and what you spend a lot of time thinking about.
Hey everyone, welcome back to Outwork with Ready, a podcast about work design and how
organizations can make change work in their favor. I'm Rodney Evans, here with my co-host
Sam Sprylin. Hey Rodney, how's it going? You know it's okay. Okay great. Well, companies,
you know those things. They're facing more change than they were built for and the problem is
organizations are still running on management ideas from a completely different era. Rodney and I
work with leaders and teams who are redesigning how work actually gets done. So change becomes
fuel of the take instead of sand in the gears. On this show, we share patterns we're seeing inside
of organizations, what's working, what gets in the way. Today, we're going to talk about how you
actually get shit done, which amazingly we've never covered on this show in this way before.
It's exciting. But first we have to check in because how you do something matters just as much as
what you do. Sam, what's today's question? Rodney, we are both of an age and I'm wondering if you
have any tech habits that clearly label you as like an elder millennial Gen X sort of person. I
don't know exactly where you fall in. For me, it's an elder millennial. But there's definitely some
things that I've caught for myself and I'm thinking about things like maybe you have an AOL.com
email address or maybe you feel like you can only make big purchases from a real computer and not
your phone, things like that. My main one that just I shake my head at myself a little bit every day
is I check Yahoo.com for the news. I don't know why it's not a good news say. It was just like a
banner there and there's like usually 15 little headlines and I'll go to Yahoo.com and just take a
look there. It's the only thing I do on Yahoo.com. I don't even understand what Yahoo is anymore.
But what it is to me is 15 news headlines that somewhat change throughout the day.
And that's got to make me that makes me old. That's really funny. That's really funny.
My answer to this question is going to be somewhat disappointing and non-specific but you can tell
that I'm older and not as like internet native as you are because I don't even know what those
things are. Like I'll watch someone younger than me do something on their phone and I'll be like
oh, I didn't even know you could do that. So it's like I don't even really know what my
tells are because I don't even know how you're supposed to do it. But I do know that whenever I'm
like observing like Alistair or Jack using literally any piece of technology, I'm like oh,
is that how you are, but oh, I didn't know. So basically it's everything. My tech habits are all
of the tech habits. I think any younger person who observed me interacting with technology would
be like bro, what are you doing? I mean, we did spend a solid 90 seconds before we started with
you being somewhat confused by what happened to your screen in terms of. Why did it make us
split screen? Oh, I do I turned it off. I get so excited when it happens because I think I want
it. Then also I don't like not having control over it. Yeah. All right. Well, I think we're
checked in now. Good check in Sam. Okay. So what we're going to dig into today came from a conversation
I had with a member of the ready about basically how you move from asset or like an idea or a thing
to action or activation like the idea of just like getting people to do shit literally anything
that's different or new. I don't think it gets enough airtime and I still have clients who think
that classic change management is the way. I think we have interrogated that idea enough on this
show to agree that it is not the way. But it still seems just mystifying for people to go from like
now we're convicted about the thing to like how do we get everybody else doing the thing? And so
that's what we're going to talk about today. Okay. So would you agree that this is a
similar idea to the like comms as change management approach like if we just comms harder everybody will
understand what's going on and we'll just do the thing. I mean, I think that's part of it. I think
there's a lot about how people believe change happens that's broken. So I think part of it like
commsing it to death is one move project managing it is one move training people is one move socialization
is one move stakeholder management is one move. There's a bunch of ways that people think this works
in none of them work. And so I want to talk about that. Okay. Great. Let's dig in there. I mean,
if you like each one of those has like its own kind of branching path that we could go down to
like really really explore. I mean, the first thing that comes to mind for me is just that information
is not understanding and understanding is not behavior change. Which I feel like it encapsulates
a lot of what you were talking there. See that again. Information. So sharing information does not
necessarily imply understanding of that information and understanding does not necessarily imply
any sort of behavior change. And I think for a lot of folks in kind of change leadership
points of view, that's a hard thing to wrap your mind around because it seems very logical
that if you understand the thing and you agree with the thing, then you would just do the thing.
Just do the thing. And I mean, that's not how it tends to go. That's not how it goes. This is
such a good nugget that I almost feel like this is the whole thing. I'm really tempted to just now
go right into a very specific example of this that I think. Let's do one. Yeah. Okay. Because you
just like unlocked something in my brain. Okay. So we just changed our structure at the ready.
And part of that was re-governing my role a strategy steward. And it is quite different now than
it used to be. And it's like a 25% role, which it did not used to be. So a trad would just like
publish it. Obviously, like trad wouldn't do anything. They'd just be like, well, the CEO does
whatever they want. Nothing ever gets written down. But let's just assume that we wanted people
to know about this change. I think like the basic move, the not even 101 move is the information
move of like I rewrote this role. Here it is. What we did was govern it as a system. And the reason
I'm sharing this, this is not an episode about governance, but I had the experience going through
the governing and election of my role where I definitely was like people are nitpicking about
things and weighing in on things that aren't going to have no impact on them. And that if we hadn't
gone through this process, they never would have even noticed. And they're digging into this
because we're doing this process. And it's kind of annoying. And what I came away with afterward,
because I didn't get a lot of reactions that ultimately changed anything. But what that process
did of saying to the whole company, here's the asset. Here's the information. Now we are going to
go through processing this where you have to ask questions to make sure you fully understand it
and give me your reactions to it, got to the understanding level. And even though for me as the
asset creator in this situation, the understanding process felt a little bit like a dental appointment.
It's not totally for me. Now sometimes when you're doing that and you're the asset maker, the
proposer, you legitimately are getting really helpful and important feedback. And I have certainly
integrated and changed assets and proposals that I made by 50% in the process. This just wasn't
one of those times. But even if you're not getting feedback that you use, it's not really for you.
It's to create that level of understanding in the end users who will be impacted by this role
in some way. Before I go into the behavior part, I want your reactions to that. That is an astute
example of a point that I was going to make around. There's a lot of work in going from
like zero to one to an asset and then sharing that one with everybody else. And as the creator of
the asset, I think it's easy to make this assumption that what you experienced in the creation of
the thing is being translated in the final version of the thing. And of course, that's not happening.
Of course not. People only see the final thing and that they haven't had that lived experience,
having to like wrestle with whatever that artifact represents. So of course, they have this like
very shallow understanding of what you just described with governance there is like a way to bring
them along, which is still somewhat time consuming, but less time consuming.
as this whole group making the thing from scratch.
- Yes, or less time consuming,
then pushing the information,
having a bunch of people passively consume it
and go, "Got it."
And then dealing with a bunch of friction later
when I'm not doing things they assume I will be doing,
I actually am living into the role
that I have articulated not the role
that I had for the last two years,
but like, you're doing work upfront
to avoid a bunch of friction later.
And I'm having like a real time aha,
because I think we are generally pretty good
at getting from the information to the understanding part,
but moving from understanding to behavior
requires something that a lot of us
don't feel very comfortable doing.
And I can think of a couple very present examples of this,
which is the next time I am going to do something differently
as a result of this new role saying,
I am now not doing this, Ashley is doing this
because we governed this role and it's no longer mine.
Or I am reserving this decision, right?
And I am going to make the final call on this
because it is the decision right
that we articulated in this role
that we all can send to do.
It's like, I'm responsible for remembering
the behavioral part that got documented,
but then also orienting everyone else to go,
we're doing the thing now that we said we were gonna do.
- Yeah, yeah.
- So if you're confused or irritated or disoriented by this,
it might be because you forgot
that we're not doing the old thing anymore,
we're doing this thing now.
- Yeah, and I think that's a really,
I could see it being an annoying thing
if you have to do it forever.
I think eventually you kind of get to the point
where it just becomes like, okay, we all get it.
But I think that verbalizing of a mental process
for the benefit of everybody else
is actually an incredibly valuable thing
to do in that kind of transitionary period between
the old way of doing things and the new way of doing things.
And not in like a, hey, you idiots, remember, we did this,
we agreed this thing, but just a very neutral sort of,
hey, you may be surprised or whatever,
because we're going from this to this,
just saying that out loud so that we're all on the same page.
I think is a useful thing, especially if you're in an organization
and like lots of things are going on.
Like your role change is not the only thing that I'm sure
that is like different between six months ago
and now so it can be difficult to keep them all straight.
So that kind of talk track,
the kind of director's commentary of what is happening
is actually I think really, really valuable.
- Totally and is also a good reminder
for the person who is instigating the change.
Like I also have other things going on.
And I also forget that actually we said
that Sam is going to make that call now instead of me.
And so it's helpful to me when she says,
I'm exercising this decision right that is new.
And you know what I mean?
'Cause like I forget too.
Like I also default to old patterns,
even when I'm the one in this case
who was like the author of the change.
So it's like, I really love what you said
because I do think that information
is the precursor to understanding
and understanding is the precursor to behavior.
And it's very easy to like take any of those as the off ramp
and be like, I think we're good.
I think we got it.
- Yeah, so in this case, it's a type of change
where it sounds like it's not particularly contentious.
It's more, it's like an update on like what we're doing
and you may not remember.
But I think there's also other flavors of like
not changing or not doing things
that are more overtly not like I just can't remember
but it's more like this change
actually does not benefit me.
So I am going to either quietly or loudly resist
or I'm gonna try to protect this thing
that the change is moving us away from
that used to be a thing that I really cared about
which I think is also a whole genre of not changing
in organizations that often our work starts to bump up against.
- Yeah, can you think of an example of that?
- I mean where my head goes is any sort of,
like prioritization changes in terms of like the work
that we're gonna do.
Like we used to do A, B and C
and they were our most important things.
We made all of our money from that
and the teams who were doing that
had a lot of power in the organization
and for various reasons related to our strategy
we are now emphasizing DE and F
and some of you folks who were working at A, B and C
maybe kind of shifting over to DE and F
and some of you are gonna continue working at A, B and C
'cause that's not going away any time soon.
But that represents a major shift in maybe how people
view themselves in the organization or what is valued
which I think is not just as clear cut
as like well not we're gonna go do the new thing.
- Right, right.
I think that's a great example.
One of the things that comes up for me that feels related
actually to what you just said about prioritization
and to the other, the sort of behavioral change part
is like I often think that we skip over the authority
piece of change 'cause I'm seeing this at a client right now.
So they're trying to roll out a new technology
to support sales and it's a really good technology.
It's like a best in class technology
and they're trying to replace some other software
that was not working as well for them.
And there's a fair amount of resistance
and there are people who are like,
well I'm just gonna keep using the old thing
because I don't like this new thing
or I don't understand this new thing or whatever.
And the old thing is still here and I still have a password
and it still has all my data in it.
So like who's gonna stop me?
And I think that is the question is like
who is gonna stop you?
Who is gonna stop you?
Often when this kind of stuff happens,
when it's like we're changing a role,
we're changing a tool, we're changing our priorities,
we're changing our strategy, we're changing something
that is real, we don't say clearly
like who has to do what when that change is made.
So what did not happen with this rollout
of this new sales technology is like first of all,
the leader of that organization,
I don't think I could be wrong, I wasn't there.
But I don't think said this technology rollout
is going to support our strategy in the following ways.
This is where we're headed and this is an enablement tool
to get us there and that's why we have to do this.
I think that part was missed.
So it feels a little bit like, well why are we,
why are we doing this?
And then as the sort of rollout crew came through,
I don't think anyone ever said like,
okay, so if you're a sales rep on Monday,
you have to start using this tool instead of that tool
for all of your calls and track all of your deals.
And the old thing is gonna be shut down on Friday.
So you better get your data out of there
and oh, by the way, the metrics that we collect
that determine whether you made your quota
and are gonna get paid also will come out of this new tool.
So Monday it is, got it?
Like people don't say that.
They're like, we're doing change management,
we're doing comms, we're posting Slack messages,
they're video tutorials and I'm like,
I do actually think the authority part gets missed
of like, what about this is non-negotiable
and in cases like this,
it isn't really a participatory decision.
Like a leader has said to do what we need to do,
we need to use this tool, so we're gonna use it.
But like it doesn't get sort of like,
communicated that way.
- Sure, all those things are kind of necessary
but insufficient on their own
without the very clear bright lines around
when things, like when you have to be into the new tool
for example, people, I'm not gonna talk for all people,
but a lot of people are really motivated
by really clear deadlines.
So you can have all of the best intentions of the world.
Like, okay, I know there's this thing,
I'm supposed to be moving into this new tool.
I know there's some stuff that I can watch about it.
I've got a vague sense of how it's better.
I totally intend to do that.
And because most organizations aren't exactly great
at protecting people's time to like think about work
and structure of their own time,
that stuff gets deprioritized.
And it's quite different when you know very clearly,
like, oh, like on Friday, the 31st, this thing goes away,
it can be a gift to be very clear about things
that are going to happen.
And people would much rather have that clarity
than a vague sense that they're supposed to be doing
something and wondering if they've actually done it correctly.
- 100%.
And having been on the receiving end of a lot of these kinds
of changes, like, including at the early days of the ready,
the good news is you don't have to like it.
And it can still happen.
It's like I wasn't particularly thrilled when we switched from Trello to Notion and no one asked
me for my opinion. It was just like this is what the company is going to be run on now. So if you want
to work at the company and also get paid, this is where you go to do that. And I was like, well I
hate this and I think it's stupid. And also it doesn't really matter. And with a lot of change,
you know, there's a lot of like what's in it for me and winning hearts and minds and blah, blah,
blah, blah, blah. And sometimes there are changes where it's just like, this is happening. So
do it. And I think it's really helpful to know which of those kinds of changes you're making.
Like, are you making changes that people need to be excited and energized by and like believe
in their heart? Or are you making a change to a sales software because you're not selling shit
and you need your sales reps to sell shit? And this is the tool that's going to help them.
Like, it doesn't really matter what they think. Ultimately, they just have to learn how to do it.
And humans like are we're like always going to resist these things. And so I do think we're
going to resist because it's like, it's unfamiliar. It's annoying. There's a cost of change.
Like, there are rational reasons to resist. And I think that to your point, clarity is really
helpful in those situations because it helps me just be like, okay, well, I'm just like grumpy
about this, but there's a shelf life on that because it's happening on Monday. Yeah. Yeah. And I,
you know, I think if you have nothing but a relentless drumbeat of these top down changes that
make people grumpy, I get a little bit skeptical. Like, all right, what exactly, like, what is going
on here? But I do think having a more nuanced take about the types of change that are that need
to be more participatory and really do need hearts and minds versus just like, honestly,
things that probably people don't really care about. If they care about, they care about it in the
like those very short term of like, this is annoying. I got to like learn a thing, but I can
learn a thing. It'll, you know, in two days, I'll be up and running. Those sorts of changes don't
need to, they are not of the same type as like a major strategic shift, for example, or something,
something else that is just maybe a little bit more more nebulous. So do we have different plays
to run for those things or do we treat everything like a huge deal even when they're, it's not.
I think that's exactly right. And I would be interesting. I don't have one in mind right now,
but it would be interesting to have sort of like a filter for like when to just be like
clear and explicit and deadline oriented and really lean into process and when to do the adoption
campaign and to really try to get people enrolled and enlisted like which kinds of things
require which kinds of motions. Just the thing off the top of my head is that my mind gets
immediately went to like complicated complex. So like a complicated tool where it's just like,
this tool just lets us do something a little bit better, like just get on board. Like come on.
Well, make sure you're like, well trained and you've got the information you need and it's just a
matter of like getting in there and doing it versus like some sort of shift and I don't know if I
have a good example off top of my head that is more like we need people, we need your intrinsic
like motivation and creativity to make this thing actually happen. That I don't think you can
really top down your way into doing particularly well. And that's exactly the shorthand. When it's
like we're moving to a different corporate credit card, everybody download the app. That's just
complicated. When it's like we're moving to a completely new brand position and we need you all
to start speaking or writing or using these kinds of visuals, that's complex. Yeah, totally,
totally. I love that. I think that's really smart. Okay, everyone, Sam figured out your
extra smart on a birthday morning. Is this our new recording time? I don't know.
Too bad or in under 30 minutes. Okay, so let's talk a little bit about why people don't do that
because what I see a lot is some version of the following. The people who are making the asset,
whether that is the brand work or the culture deck or the new org chart or the strategy,
whoever sort of has the pen on making the thing, spends a lot of time like beautiful minding,
and maybe is getting feedback, but not including the end users. Maybe is getting feedback from
like a closer or safer or more insular circle. And then they spend a lot of time perfecting.
I'm just going to call it the asset for shorthand. And because that has taken so much time
and so much labor and so much love, they're like, we're done. Big bang reveal. Why do people do that?
This is a point. And then reality punches back. And reality is like, I don't think you are done.
I think you're just at the starting line. Yeah, I think there's probably a lot of reason
that's why I think where my head just went to is that on the off chance that that works,
like you do the big reveal and people are like, oh yeah, this is cool as hell, like good job.
That feels really good. And I'm not saying that's impossible to happen. Like you can potentially
make something like that. And you know, you get that sort of reaction and you feel like you really
nailed it. Like your craft is being respected and people are like, oh, this is so great.
So that chasing that dragon, I think sometimes for that process that ultimately
results in the real, the real letdown. And I also think what makes you good at creating
an asset is likely not the same skill set for creating a process for bringing people along
into that. So like if you are an expert brand designer and you make dope brand designs and you go
off into your brand cave and you come back bringing the tablets of the new brand, like that's
all within your expertise as a professional. But the like the service design of like bringing
people along to contribute to that is probably not like what you went to school for and what you
spend a lot of time thinking about. So I wonder if people shy away from that messier process of
bringing people along or getting feedback because it is somewhat outside of their expertise.
I used to think a lot about this at my old job because I had a real tendency to like be in the cave
and then do the big reveal and then like the organ would get rejected. And I was just and I would
just be like, that's because you don't see my juice. Yeah, exactly. You don't understand me.
Which is also true as incidentally, both things can be true.
And one of the reasons that I did that is because I actually found significant feedback
quite difficult to integrate to work in progress. If someone gave me feedback when the idea was
like half done. And they were just like, this is like completely off base. This should be like this
and blah, blah. For my brain at the time, I found it very difficult A to like sort of have the
discernment or like the taste level to go like, okay, this is what about that is really right on
and I should integrate this. And this is what I can willfully ignore. And like this is really
going to make it better where my mind would usually go is like, I have to start over or I have to
shut this person up. And I don't know what changed for me in the last like 15 years that I don't
feel that way anymore. And I feel like even if in feedback on work in progress, people tell me
some truly wacky shit, I feel like I have a pretty good way of using it helpfully to make work
product better. But I didn't always. And I don't know how I learned to do that. But it I think it
really changed my posture on getting feedback. Because now I really trust that whatever the end user
throws at me, I'm going to use it for good. And like it's going to be helpful. And it's not going
to be derailing. But I don't know how that happened. Yeah. Well, I mean, I think what you're describing
is is the development of taste, right? Like you you're you're basically saying that early on before
you really had developed a sense of taste, it was hard to tell whether the feedback was useful or not
on base off base, whatever. Now that you've gotten a bunch of reps, developed a bunch of taste
around this feedback is something that is filled with more information that you can actually
do something with. And you have the skill set now to incorporate it into a work in progress and
not have to kind of go back to the drawing board every time somebody shares something with you that
is not what you had in mind. Yeah. I also think this is a place where AI is really really useful.
Like once a day, I will feed AI like a draft of something that I'm working on and like
granola notes of a round of feedback that I've gotten on it and be like, give me a new draft
with the best of these insights incorporated. And it's like, yeah, pretty good. It takes a lot of
processing out. I say this because I think the big reveal like we made a perfect asset and now we
just need to socialize it and get people to use it. I feel like it's so so common and I do think
that there are like some behavioral roots and I'm just I'm conscious that there's fear of failure.
There's like fear of conflict. There's fear of criticism. There's like a lot of stuff wrapped
up in it and also I just see in myself the way in which for a long time I just didn't have the
ability to effectively integrate feedback and I think it's like a skill to develop and it makes
work in progress much less scary when you're like I can always find a way through this. It's a
different way of being. Yeah a few years ago there was a quote going around at least in the
various circles that I travel from Ira Glass talking about taste. Are you familiar with that?
No but it's it's long so I'll try to just oh tell me tell you the whole thing let's give
Ira Glass an airtime on this show. It's pretty it's pretty well. It's the reason I have a podcast.
Okay so he says nobody tells us to people who are beginners and I wish someone had told me
all of us who do creative work we get into it because we have good taste but there's this gap.
For the first couple of years you make stuff it's just not that good. It's trying to be good
it has potential but it's not but your taste the thing they got you into the game is still killer
and your taste is why your work disappoints you and a lot of people never get past this phase they quit.
Most people I know who do interesting creative work went through years of this it was only by going
through a volume of work that you will close that gap and your work will be as good as your ambitions
and I took longer to figure out how to do this than anyone I've ever met it's going to take a while
it's normal to take a while you just got to fight your way through and I think that's that's the
experience thing right and I think what we sometimes just collapse down into experience or age
or wisdom is what he's talking about right there it's the reps of actually doing it a bunch of times.
Yeah okay side note I lived in New York City for a long time and the only time in my tenure
of New York City that I was actually Starstruck was when I saw Ira Glass and I basically stopped in
the middle of the sidewalk and grabbed onto its arm and I was like this Ira Glass and he was like
what an ad who was not undone by seeing Ira Glass in the wild was like he Ira and his wife were
like reading you know one of those like stands with like a menu on it outside of a restaurant and
Ed was like you should go just normally people like us just people like us he goes you should go
ask him I feel read that brunch menu allowed to it's like no and then I ran away instead good one
Ed anyway Ira I hope you hear this your biggest fan um yeah I think that's right Sam and the other
thing as you were reading that that I realized is part of the reason that I also used to be afraid
of feedback was because I was afraid of how much work it would take to redo something
sure yeah and there are a couple of ways to get out of that one is don't finish it before you show
it to anyone and then you won't be so precious about it because you won't be like I I thought I was
done um and two is I feel like now what I know is if I wait too long and then I have to redo work
it's actually more time consuming than if I iterate along the way and so even if the iteration
that I'm having to make is big and unwanted I still know it's less work ultimately than if I try
to like push it and pray at the end it's realizing that when you're getting to the phase where
you're asking for feedback you're not anywhere close to being done uh I think an example of that
is like if you if you watch or if you hear a really seasoned novelist talking about their writing
process and like getting the first draft done in my head of a guy who's never written a book I'm like
first draft done like you're almost there you you've got the whole barely started a hundred thousand
words and and novelist being like yeah that's like kind of when the work starts um you know I'm
going to rewrite this thing like two or three times and I'm not anywhere close to being done and
that's just like a that's the difference between someone who has done a thing a lot of times and
someone who has kind of a rough grasp of what it actually takes I think that's exactly right um what
else should we talk about in terms of making work happen um I think I have one one other thing maybe
that that we haven't directly hit I don't remember who I first heard talk about this some
somebody working in change work but really tend to looking at it through a marketing lens so when
you are doing marketing you don't just kind of define like the one person that you are trying to
market to like there are there are um personas and like getting really specific about the different
sorts of people who you're targeting with your messages and which message you're targeting to
which sort of persona and like where are they in the funnel and I think it is interesting to think
about change work um using a similar idea in that there's a bunch of different types of folks who
are potentially going to be participating in this change and they are very different from each other
and it is tempting to kind of lump them all together either into just like one group of just like
people who need to change or in just some like really um course groups of like these are the people
who are stoked about it and these are the resistors and that's the two groups that we're kind of
talking to I I think there's something interesting about getting much more specific about the different
personas that exist within any sort of change effort and then and then doing interesting things
in terms of how you talk to them in the experiences that they need and this is obviously more in the
realm of the type of kind of complex change not the one reason I tell people what to do but if you're
going to be in this complex sort of change space then I think you need to bring some you got to
kind of meet complexity with complexity you can't oversimplify it and trust that you're going to
get to a good place I think that's right and it's also like in you I see this a lot in M&A
which like is a very complex change to bring two complex systems together and it's usually unclear
if like one is eating the other or you're trying to like blob tag them or what's happening um is
there's not a lot of that persona work of of like what does this mean for you for you
Sam as the end user versus for you Rodney is a different end user and what do we need you to do
differently and what's going to change for you on Monday and it's like if things are just going
to change and you can be a passive consumer of that then like probably that's not that hard if
if things are gonna change and like we need you to alter your behavior as a result of that because
of a specific role that you play it's probably like a different motion with you in terms of like
understanding your relationship to this change your appetite for it your support blah blah blah blah
so I think um I think that's really smart and you know we've talked on this show before about
like the cake baking problem and I this is essentially what this is it's just the idea that like
it's very easy as any kind of creator to go away and make the world's most beautiful cake and then
bring it out to a group of people who didn't ask for it who don't particularly want it and then
be really disappointed when you're like but cake is good you should have this but that's not that's
not like thinking about the end user it's not designing with the end user in mind um which great
marketers absolutely do yeah yeah for sure should we talk about some specific things to do yeah let's
talk about what to do Sam you go first right okay um my first thought is about kind of love what
does it look like to lower the activation energy for people to participate in something um I'm
thinking about this right now because I'm doing a project with an organization where you know
that everybody is at 110% at least uh allocation and there's no time to really do anything but
there's this group of people who have hand raised they're gonna work with me as a core team to
to figure out a thing that we're gonna do for like a design sprint and I have really tried to focus
on making it extremely clear how they can play and how they should play right now because I've
really gotten the sense that they want to contribute but they do not have any time to just like
figure shit out so we've been doing some asynchronous work over the last couple of weeks and I've
kind of been going back to like my high school days of like writing instructions on the worksheets
it's like here's precisely what I want you to do like take no longer than 20 minutes to do it here
are the three questions send me your answers when you're done and just really trusting the fact that
while it feels a little like top down it's really serving it's meeting them where they actually are
and helping them actually contribute and I've been thinking a lot more about where are other places
to do that where can we give people the gift of clarity to in terms of how to play
and not kind of just invite them to an open space it's just like hey what does like figure it out
as we go along which there's always a time and a place for things like that but I've been
kind of leaning into the opposite of that a little bit more nowadays I love that
think that's great. What do you got? And the thing just to add to that is like you're treating
the activation as the real work. In that case, like you're not overly concerned about
the asset or the thing. And it's like the work to be done is this interstitial stuff.
Yeah. I want your actual answers to these questions because we're going to use that for things
coming up in the future. I don't want to like waste your time. You figuring out that stuff. Totally.
I can just tell you that. Okay. I'm going to talk about socialization because people think about
socialization as being an event or a series of events. And it's not. It's like a system. And
people think that you go asset, socialization done. And that is not correct. So here's what doesn't
work. Just talking a bunch about stuff doesn't work. Having office hours and thinking
anyone is going to show up to them to learn about this thing that they don't give a shit about
also does not work. And anything that's in a deck basically is not going to work. Those are the
things that I wouldn't do. And when I say in a deck, I don't mean as the asset I mean as a
presentation, like you can just assume that people have gone on a little mental vacation or
open to their phone. If what you're doing is running them through a deck.
Here's the sort of arc that I generally follow when I'm trying to do something new. First is
early signal. Something's coming. Something's coming in this vein for this reason.
This is the tension. Let's all understand the tension. Eventually you are going to see a proposal
to solve this tension, but not right now. And I will telegraph that shit every single week
for six months until there's a proposal. Just to be like, I know we're still feeling the tension,
tension, right? Proposals coming. Then when we introduce the new thing and you've seen this
authority, I have a tendency to start with narrative and why and emotion. So a lot of times before
the big reveal, I'm like, here's a video explaining why we're doing this work and what it means
rather than here's the asset. So it's like, we've gone from the tension to the origin story
and the emotion around it. Then the launching of the thing with a specific ask, here's a document,
get in there and drop comments. Here's a proposal. We're going to govern it on Friday.
Here's the deck. I would like your feedback on the following three slides with this client persona
in my specific asks to get people marinating. Then some kind of interactive forum, which we've
talked about can be generative, can be governance, can be feedback oriented, can be whatever you
want it to be, and then some kind of ongoing reinforcement, which we've also talked about like
narrating the adherence back to the change. To me, that's what a system of socialization looks like,
not, I shipped it and I'm available for questions. Which is what I frankly usually see.
Yeah. What I love about what you just described there. I know narrative was like a step in it,
but also the whole thing is kind of like a narrative arc as well that has like a shifts in energy
and ways to interact and ways to be thinking about it and like a pleasing sort of like conclusion.
Totally. I think in the best case, that's exactly what it is.
What else you got? I got one last one, which is just, and I feel like this is actually a piece of
advice that I've given on lots of different episodes, which is an interesting pattern, but
stop doing things, remove, remove things, remove, remove, remove, stop, make space, stop, remove,
change. If you want people to do something different, that is not in most cases a like one-to-one
replacement. Like doing something new takes extra attention and energy and time. And if you are not
creating any space for that, then that is not going to be done particularly well. People aren't
going to put much time into it. They're not going to think about it that much. So if you're asking
people to do something that requires more of them, do your best to try to make more space for that.
I love that. That's really cool. I mean, always, always more space.
Always, for all the things, right? Usually I get more space. My last one, which came from a client,
I'm going to send this to her, but I thought there's so smart. We were leaving an offsite a few
weeks ago, and basically we had like a follow-up for the rest of the team, and we've tried to do
the same follow-up move before, and we haven't gotten a lot of traction even though I know that it
would really be beneficial to them. And basically, I was trying to get them to move into proposals based
on the work that they've done, and that has not gotten traction. And so she was like, let's like
in a document put all of the proposals that need to be made with like a couple of lines of notes.
And the overarching advice that I thought was so smart was that she was like, don't make it too
pretty. She was like, leave it ugly, leave it drafty, because part of the problem is when you
give people something that looks really polished, and you ask them to interact with it,
they then feel like they have to do a lot of work to respond with polish. And actually,
this does not require polish at all. Like this isn't going anywhere. We literally just need people
to write three bullets on what they want to do next, like no punctuation, no intention behind it.
And I thought it was such a smart design choice of like, keep it ugly so that they can be scrappy,
because that's actually what we need. And if you give them something that feels overdone,
they're going to not do it because they don't want to overdo it.
Yeah. Yeah. No, that's that's so good. And it's so simple. I love this idea of like,
keep it ugly as long as possible. Keep it ugly. I feel like I feel like that
like works in a lot of different contexts. It really does. My personal life.
I was going to send you up for that.
So rude. I would never say that to you.
I know that's why I said it to myself. No, that's so good though. I like I like that. I feel like
it's like that type of thing that I've never articulated, but I've like felt in my bones.
I've definitely had people share things with me. And I'm like, oh my god, I can tell
so much time has gone into this. If I don't have anything good, like really good to offer,
I'm just going to like kind of throw my hands up and be like, good job, dude, like you.
Right. Right. It does not feel like this is like wet clay that's still to be molded.
It feels like this came out of the kiln. And anything that I do is potentially
going to break it. Totally. Well, and to my point, my last one about the time thing,
if I'm also feeling like pressed for time and you hand me a pretty thing to get feedback on,
I'm like, all right, this is going to take some time for me to really engage with this and give
you what it deserves back. I'm not going to do that. So like, it's just not going to happen.
Keep it ugly, folks. Keep it ugly. All right. Are we done? Did we do it? We're done. We did it.
Great. Hey, everyone. That's right. I'm talking to you. We're always looking for new topics
for the show. So if you have an org pattern that you're having trouble changing, shoot us a note,
podcast at theready.com. This show is edited and mixed by Taylor Marvin at Coop Studios
and produced by Jackman Amberg. Outwork with The Ready is created by The Ready where we help
organizations around the world and change the way they work. Thank you for listening.
[BLANK_AUDIO]
Podcast Summary
Key Points:
Information sharing does not lead to understanding, and understanding does not guarantee behavior change—highlighting a critical gap in traditional change management.
Effective change requires moving beyond top-down communication to include participatory processes that foster real-time understanding and shared ownership.
The transition from idea to action often fails because creators assume their experience of a change mirrors the end user’s experience, leading to misalignment and resistance.
Clear authority, timelines, and behavioral expectations are essential for adoption, especially in complex changes where ambiguity breeds resistance.
Designing for participation—through low-barrier, iterative, and “ugly” drafts—reduces friction and enables users to engage without the pressure of perfection.
Change success hinges on a narrative arc
Organizations often skip crucial design work in the activation phase, treating change as a one-off event rather than a process requiring ongoing support.
The skills to integrate feedback and iterate on work in progress are developed over time through experience, and are distinct from expertise in creating assets.
Summary:
Organizations often fail to move from ideas to action because they rely on top-down communication and assume that sharing information leads to behavior change. This episode emphasizes that understanding and behavior are separate stages, requiring intentional, participatory design. Effective change involves creating a narrative arc—building tension, explaining the "why," and guiding users through a system of feedback and reinforcement.
Key to success is clarity around roles, timelines, and responsibilities, which prevents confusion and resistance. The creators of change—like brand designers—often excel at crafting assets but lack experience in engaging people. To overcome this, change initiatives must prioritize low-friction activation, such as simple, "ugly" drafts that encourage quick, scrappy contributions.
These processes build trust and reduce the mental load on participants. Ultimately, change is not about broadcasting a message but about designing a shared journey that includes people at every stage, from tension to action. This approach transforms change from a source of friction into a manageable, human-centered process.
FAQs
Information doesn't automatically lead to understanding, and understanding doesn't necessarily result in behavior change. People need active engagement, feedback, and clear context to internalize and act on new ideas.
Feedback helps users understand the change by engaging them in the process. Even if feedback isn't used directly, it creates understanding and builds shared ownership, especially when people are involved in governance or decision-making.
They skip the participatory process of co-creation and understanding. The change is presented as a one-way transmission, not a shared journey, leading to disconnection, confusion, and resistance.
By leaving proposals or documents drafty and unpolished, people feel less pressure to respond perfectly. This encourages quick, scrappy input, which increases participation and reduces the barrier to action.
A socialization system includes early signals, narrative storytelling, interactive feedback loops, clear action asks, and ongoing reinforcement—acting as a continuous narrative arc, not a one-time event.
Change requires more time, attention, and energy than the old way. Without creating space for this, people will not engage deeply or sustain the new behavior over time.
Chat with AI
Loading...
Pro features
Go deeper with this episode
Unlock creator-grade tools that turn any transcript into show notes and subtitle files.