What Leaders/Managers Can Learn from Creative Confidence
Managers are often rewarded for having the answer fast, so the habit that forms is announcing a decision in the first meeting rather than getting close enough to the actual work, or the actual team member's obstacle, to know if that decision fits. Some managers also quietly opt out of creative problem-solving altogether, treating it as a "special" skill for design teams rather than something they use in ordinary planning.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 4 selected
The core lessons, applied to you
Get close to the real problem or the people affected by it before jumping to solutions
A manager's version of this is walking the actual workflow with the people doing it, rather than reasoning about it from a dashboard or a status update.
A manager notices a project is behind schedule and immediately mandates a new daily check-in to "improve accountability." Two weeks later the real cause turns out to be a broken handoff between two teams that nobody had asked about directly.
Before proposing a fix for a recurring team problem, spend thirty minutes watching or asking about the actual step where things go wrong, rather than reasoning from the summary you've been given.
Generate many possible ideas before judging any of them
Because a manager's opinion tends to carry outsized weight in the room, floating just one option early can quietly shut down better ones before they're spoken.
In a planning meeting, a manager opens with "I think we should just reorganize by region," and the room spends the rest of the hour debating that one option instead of surfacing three or four others that were never said out loud.
In your next planning discussion, ask the team to generate at least three options before you share your own, and write all of them on the board before any is discussed.
Build something rough and quick to test an idea, rather than perfecting it in your head first
A manager can pilot a process change with one team for two weeks instead of rolling it out company-wide on a hunch.
A new performance-review format is rolled out to the entire department at once, based on how well it sounded in a leadership meeting, and it takes a full review cycle to discover it doesn't fit how half the teams actually work.
Before rolling out any new process to the whole team, run it with one small group for two weeks and gather their reaction before deciding to scale it.
Treat early failure as useful data and iterate from there
When a new initiative underperforms in its first weeks, a leader who reads that as specific, fixable information — which part of the process didn't land, and with whom — moves faster than one who either abandons the idea outright or defends it out of pride. Modeling that response also teaches the team it's safe to bring forward their own early, imperfect attempts instead of hiding them until they're polished.
Involving the team in generating options can feel slower than just deciding, especially under deadline pressure. But a decision the team helped shape usually needs less rework and less persuasion to implement, which often makes it faster overall.
Name one thing, honestly
Where in your team's current work are you directing a solution before anyone has confirmed what the real obstacle is?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Before rolling out any new process to the whole team, run it with one small group for two weeks and gather their reaction before deciding to scale it.