What Career Professionals Can Learn from Creative Confidence
Many professionals settle into "how we've always done it" for recurring tasks — a report format, a process, a way of handling client requests — without ever revisiting whether it still fits the actual problem in front of them. It's also common to assume creative problem-solving belongs to the "creative" job titles, and to sit out any brainstorm or process redesign because that's "not my role."
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
Before proposing a fix to a recurring workplace annoyance, it's worth confirming what the actual bottleneck is for the people affected by it, not just for you.
An employee assumes a slow approval process is caused by too many sign-off steps and pushes to cut two of them, only to learn afterward that the real delay was one specific reviewer's backlog, which the change did nothing to fix.
Before proposing a process change, ask two or three colleagues who deal with it regularly what specifically slows them down, rather than assuming you already know.
Generate many possible ideas before judging any of them
Under deadline pressure, it's tempting to run with the first workable approach to a task rather than spending a few minutes considering alternatives.
A team defaults to the same slide format for every client presentation because it's what was used last time, without anyone considering that a different structure might communicate the specific findings more clearly.
Before starting a recurring deliverable, spend five minutes listing two or three different ways to structure it, even if you expect to land on the familiar one.
Build something rough and quick to test an idea, rather than perfecting it in your head first
A rough draft circulated for feedback early saves far more rework than a polished version presented for the first time at the deadline.
An employee spends a full week perfecting a proposal internally before sharing it, only to learn in the first review meeting that the entire approach needed rethinking — feedback that a rough one-page outline could have surfaced on day one.
Share a rough, one-page version of any significant deliverable with a colleague or manager before investing more time polishing it.
Treat early failure as useful data and iterate from there
A proposal that gets rejected, a pitch that doesn't land, or feedback that stings in the moment is ordinary information about what didn't fit, not a signal about long-term competence. Professionals who look closely at the specific reason something didn't work — timing, framing, audience — tend to come back with a sharper version rather than either repeating the same approach or avoiding that kind of work altogether.
Gathering more input before proposing a change can look like slowing things down in a fast-moving workplace. In practice, a short round of real conversations usually prevents a proposal from stalling later over an objection that could have been caught early.
Name one thing, honestly
What's one process or deliverable at work you've never questioned simply because "that's how it's done," and what would it take to test a different version of it?
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
Share a rough, one-page version of any significant deliverable with a colleague or manager before investing more time polishing it.