Creative Confidence

1. 1Name the specific snake. Write down whether your block is fear of being judged, fear of getting started, or fear of the unknown—each has a different remedy, so don't treat them as one.
2. 2Convert the fear into a series of small successes. Instead of one high-stakes attempt, design a sequence of low-risk steps you can win at, the way Bandura cured decades-old phobias by guiding people incrementally toward touching the snake.
3. 3Do a bad job first. Suspend judgment and get something crude into the real world—write the 'bad ad' describing your finished product, corny and quick, before you let quality standards paralyze you.
4. 4Lower the stakes deliberately. If the problem feels like everything hinges on it, make it less important: list a dozen possible options instead of hunting for the one perfect answer.
5. 5Create peer pressure and gather an audience. Put another person in the room even if they give no feedback—social commitment forces you to show up and moves the idea out of your head into words.
6. 6Reframe every attempt as an experiment. Adopt Edison's stance that a failed experiment isn't a failure if you gain constructive learning; count your shots at the goal, not your success rate.
7. 7Go wide before converging. When an open question hangs in the air, resist the trained urge to blurt the cliché answer—identify many possible approaches first, then pick the best.

Doug Dietz spent two and a half years designing a GE MRI machine he was proud of, until he watched a terrified little girl cry on her way into it and learned that up to 80 percent of pediatric patients must be sedated to be scanned. Pride turned to feelings of failure for letting down the patients he meant to help—a personal crisis that could have ended in quitting or resigning himself to the status quo. Instead of letting that fear of failure stop him, he told his wife he had to make a change and sought advice from friends and colleagues. His boss pointed him to a d.school executive workshop, and Doug flew to California not knowing what to expect but eager to embrace any new method. There he learned a human-centered approach: he observed and talked to real users, built crude prototypes with managers from other industries, and iterated on the ideas of others. The cross-pollination left him more creative and hopeful than when he arrived—he had touched the snake instead of avoiding it. His failure became the raw material for reinventing the child's MRI experience.

• If an unresolved problem makes you anxious to blurt the first answer and move on, then stop and go wide—generate many options before converging, because the first idea is usually the cliché already in your head.
• If you can't get started, then put a person in the room and gather an audience; if you still stall, do a bad job on purpose just to get something out there.
• If the problem feels so important that everything hinges on it, then lower the stakes and make it less important so indecision doesn't paralyze you.
• If an experiment ends in failure but you gained constructive learning, then count it as progress, not a failed experiment—more shots at the goal is the math of innovation.
• If you catch yourself thinking 'I'm not good at that kind of thing,' then treat that belief as the block to remove first, because skills are not set in stone.

• Rushing to judgment: like the med student who immediately proposed 'a new kind of coffee creamer,' you converge on the first answer because unresolved issues feel uncomfortable—the tell is relief the moment you name any solution.
• Staying stuck at the planning stage. The need for control keeps you refining the plan instead of leaping into action—the tell is you feel busy but nothing has left your head into the real world.
• Believing creative geniuses rarely fail, so you interpret your own failures as proof you lack talent—the tell is you quit after early setbacks instead of running more experiments like Mozart, Darwin, or Edison's thousand attempts.
• Suppressing sacrificial concepts by critiquing wild ideas too early—the tell is the room goes quiet and no one offers the impractical idea that could have led to a breakthrough.
• Resigning yourself to the status quo or to what others told you to do—the tell is you benchmark against competitors and just 'tweak around the edges' instead of rethinking the experience.

• ▸Name the snake: which fear is blocking you—judgment, getting started, or the unknown?
• ▸Worst-case reframe: what actually happens if this fails, and what could you learn from it?
• ▸Lower the stakes: rewrite the task so it is small and low-risk (list options, not the perfect answer).
• ▸First small success: the smallest step you can win at in the next 30 minutes.
• ▸Bad job version: describe the crude 'bad ad' or rough prototype you'll make before judging quality.
• ▸Audience/peer: name one person you'll put in the room or talk your idea through with.
• ▸Experiment count: how many shots at the goal can you take this week?
• ▸Growth check: cross out any 'I'm not good at that' belief and rewrite it as changeable.

1. 1Name the specific fear blocking you—fear of being judged, fear of getting started, or fear of the unknown. Bandura found the biggest snake in the room is fear of failure; you cannot dissolve it until you locate it.
2. 2Design a first step small enough that success is near-certain. Guided mastery works because doubt is cured by a series of small successes, not by pep talks—so shrink the ambition, not the intent.
3. 3Get direct experience rather than instruction. Being told to innovate has limited effect; complete one full design thinking cycle yourself so the value is felt, not checked off as a box.
4. 4Reinterpret each attempt as data. Treat every experience as something to learn from instead of a verdict on your worth; this is what lets you leap from planning into action while still uncertain.
5. 5Recruit a coach or catalyst who guides you through mastery the way a golf instructor coaches driving up the fairway—practice plus feedback, one person at a time.
6. 6Stack the next slightly harder success on the last one, deliberately raising your sights so persistence and resilience compound.
7. 7Treat building your own creative confidence as your first creative challenge: ask what action you can take today, right now, and accept the uncertainty rather than waiting to feel ready.

Doug Dietz, an award-winning designer at GE, discovered that children were terrified of the beautiful MRI machines he had built—some had to be sedated to be scanned. Rather than resigning himself to the status quo, he started with empathy and took a small, concrete first step: he gathered a group of volunteers to re-imagine the scan as an adventure. They re-skinned the machine and room into an 'MRI pirate ship,' turning a frightening procedure into a story. The payoff came when a young patient who had just been scanned tugged her mother's skirt and asked, 'Mommy, can we come back tomorrow?' That single question made all his effort worthwhile. Less than a year after this epiphany, Doug's creative confidence had visibly grown—an example of self-efficacy built through one guided success rather than a personality trait he was born with.

• If someone in power just tells people to be more innovative, then expect limited effect—switch to guided mastery: get individuals through one hands-on cycle instead.
• If a project stalls at the planning stage, then the block is need for control; take one small action to become comfortable with uncertainty rather than perfecting the plan.
• If a person insists 'I'm not creative,' then treat that as a fixed-trait myth to disprove through action, not an argument to win with reasoning.
• If you're waiting to feel confident before starting, then invert it—confidence follows action taken one step at a time, so start now with whatever you can do today.
• If people add a token user slide just to satisfy a boss, then they're checking a box, not building belief; require them to complete the cycle firsthand until they 'see the value.'

• Trying to build confidence by reading, thinking, or talking about it alone—the tell is lots of enthusiasm and zero action taken, since confidence only comes through experiencing small successes.
• Making the first step too ambitious, so it produces failure instead of mastery—the tell is that the person retreats and their belief system hardens rather than shifts.
• Mistaking top-down mandates for capability-building—the tell is employees 'checking off a box' (the user slide) without seeing any value in the method.
• Treating failure as a verdict rather than a learning opportunity—the tell is paralysis at the prospect of being judged, keeping the person stuck before they start.
• Assuming creative geniuses rarely fail and comparing yourself to that myth—the tell is quitting after a first miss, when in fact prolific creators produce many failures alongside successes.

• ▸Creative challenge: state in one sentence what change you want to create.
• ▸Named fear: which snake—being judged, getting started, or the unknown?
• ▸First small step: a success you're near-certain to achieve today.
• ▸Coach/catalyst: who will guide and give feedback (facilitator, co-conspirator)?
• ▸Direct experience: the full hands-on cycle you'll complete, not just observe.
• ▸Reframe rule: how you'll read a setback as learning, not verdict.
• ▸Next rung: the slightly harder success you'll attempt after this one.
• ▸Action today: the specific thing you're prepared to do right now.

1. 1Name the recurring question that surfaces when status and money fall away: David Kelley, mid-cancer in 2007, asked 'What was I put on Earth to do?' Write your own version and answer it in one sentence about who you want to reach.
2. 2Convert a passing comment into a personal mission the way John Keefe did—when you notice a problem that stirs you, commit to a same-day or same-week deliverable rather than a quarterly plan, so passion gets tested against action immediately.
3. 3Locate the intersection of what you're good at, what you enjoy, and what you're paid to do—Doug Dietz was paid and skilled at MRI design, but the frightened girl in the hallway exposed where meaning was missing; find your equivalent hallway moment.
4. 4Reframe duty into passion by observing the actual human on the receiving end of your work; step out of the design-award mindset ('Oscars of design') and into the patient's fear.
5. 5Build creative confidence as a muscle through repeated effort and experience, since Dweck's growth mindset holds that potential is unknowable—assume your alignment can be developed, not that you're born aligned or not.
6. 6Run many experiments and pay close attention when something unexpected moves you; Pasteur's 'prepared mind' means the passion signal often arrives as a happy accident you must notice instead of clean up.
7. 7Avoid keeping all your eggs in the 'going deep' basket—pair depth in your craft with breadth of roles and encounters so the heart-vs-dollar sweet spot has more surfaces to appear on.

Doug Dietz, a 24-year GE veteran, spent two and a half years designing an MRI machine and arrived at the hospital expecting to pat himself on the back—his system had been submitted for the 'Oscars of design.' That is the pure dollar/status frame: he even admits he used 'a perfect example of bad interviewing technique' with the technician. Then a frail, sniffling girl walked past clutching her parents' hands, her father straining to say 'You can be brave.' Doug got choked up because the same machine that won awards terrified the child it served. The gap between recognition and meaning became visible in a single hallway moment. That confrontation—paid, skilled, but not yet aligned with human impact—is what turns duty into passion. The lesson: your award-worthy competence is not the same as your calling until you observe the person actually living with your work.

• If your mind leaps to awards and recognition before it leaps to the person served, then you're in the dollar frame—go find the hallway moment.
• If you catch yourself thinking 'I'm not the creative/aligned type,' then treat that as a fixed-mindset flag to drop before proceeding, per Dweck.
• If a colleague's offhand complaint stirs genuine energy in you, then convert it into a personal mission with a deadline measured in hours, not quarters (Keefe's 'Give me till the end of the day').
• If a task is only duty with no enjoyment and no distinctive skill, then it sits outside the sweet spot—don't build your legacy on it.
• If an unexpected reaction or accident emotionally grabs you, then stop and understand its significance rather than rushing to erase it (Goodyear's spilled rubber).

• Chasing the 'Oscars of design' while never watching a real user—the tell is you can describe your product's features but not the fear or joy on a customer's face.
• Assuming alignment is a fixed trait you either have or lack—the tell is you decline the 'course that would improve you' like Dweck's fixed-mindset Hong Kong freshmen.
• Talking about passion instead of showing it—the tell is you explain what your calling is rather than saying 'I can get you results next week' and delivering, as Keefe does.
• Mistaking passion for a single lucky spark—the tell is you wait for serendipity while running zero experiments, ignoring that Goodyear had toiled for years before the stove.
• Going all-in on one deep specialty and calling it your calling—the tell is you've kept every egg in the 'going deep' basket and never tested other roles where the heart-dollar overlap might be stronger.

• ▸What was I put on Earth to do? — answer in one sentence about who you want to reach
• ▸Good at: — list skills others already pay you to use
• ▸Enjoy: — list activities that energize you regardless of pay
• ▸Paid for: — list what actually generates income now
• ▸Hallway moment: — describe one real person affected by your work and their emotion
• ▸Fixed-mindset belief to drop: — the 'I'm not the type' story blocking you
• ▸Same-day mission: — one stirring problem you can prototype within 24 hours
• ▸Experiment log: — three small tests you'll run to surface unexpected passion signals
• ▸Sweet-spot statement: — one line naming where all three circles overlap

1. 1Separate the two barriers before you intervene: for non-artists, offer reassurance and a basic drawing lesson so they can sketch; for skilled artists, give explicit permission to set perfectionism aside and draw a few rough lines. State plainly that the culture judges the quality of ideas, not the quality of sketches.
2. 2Establish a visible meritocracy: commit that every idea gets fair consideration and can be judged across divisional and hierarchical lines. Say it out loud so people trust it and pour their creative energy in rather than protecting themselves.
3. 3Open each team meeting with a personal check-in — go around one by one with 'How are you doing, really?' or 'Share something personal about yourself' — so people bring their whole selves and creative thought isn't taxed by compartmentalizing.
4. 4Run the d.school team principles at kickoff: map each member's strengths and kryptonite and divide work accordingly, name diversity as the source of both creativity and conflict, and craft the team experience in advance by agreeing on how you'll help each other and what principles you'll abide by.
5. 5Assemble a personal advisory board — a small standing group that meets on a fixed cadence to reinforce or challenge your point of view and remind you a group stands behind you.
6. 6Build or join a supportive network deliberately: audit who you spend time with at work, seek out creative supporters, and avoid people whose default mode is negativity. Start a group via a tool like Meetup or an all-volunteer after-hours project team if none exists locally.
7. 7Practice in low-stakes reps: walk up to a whiteboard in an empty room, draw an idea just for practice, then draw it again — baby steps that move you from fear toward the joy of getting an idea across.
8. 8When diverse viewpoints produce 'creative abrasion,' have the risky conversation rather than shying away from it — treat the dynamic tension as fertile ground and work conflicting opinions until a new idea emerges.

Stephanie Rowe, a self-described 'hard-core analytical person' with two decades as an executive, took a design thinking workshop and then felt isolated in Washington, DC. She vowed that if she couldn't find kindred spirits locally, she would move to California. Instead of relocating, she used the community-organizing network Meetup to start a single gathering dedicated to spreading design thinking. That one gathering grew into an active group of over a thousand people. As her supportive network expanded, colleagues began telling her, 'Wow, you're so creative' — feedback she found awesome yet still odd to hear. She credits creative confidence with changing her sense of community and what she does in it.

• If team members believe every idea gets fair consideration across hierarchical lines, then expect them to work harder and persist longer; if they don't, then energy goes into self-protection instead of ideas.
• If the person is a non-artist hemmed in by timidity, then give reassurance and a drawing lesson; if they're a skilled artist hemmed in by perfectionism, then give permission to draw rough lines.
• If you're choosing collaborators or feedback sources, then seek creative supporters and avoid those whose default mode is negativity.
• If diverse viewpoints create conflict, then have the risky conversation rather than shying away from it — that's where new ideas emerge.
• If you feel pressure to generate every idea yourself, then acknowledge you don't have all the answers and build on others' — humility takes the pressure off.

• Judging the sketch instead of the idea — the tell is talented people staying in their chairs, so good ideas go unexpressed and talent goes untapped.
• Leaving personal life out of professional life — the tell is flat, guarded meetings and creative thought that quietly takes a toll; missing check-ins are the signature.
• Avoiding the risky conversations that diversity requires — the tell is a team that says it values diversity but never surfaces conflicting viewpoints, so abrasion never converts into new ideas.
• Surrounding yourself with skeptics whose default is negativity — the tell is ideas outside the norm getting shut down before they're explored.
• Trying to innovate solo out of pride — the tell is mounting pressure and no sounding board to reinforce or challenge your point of view.

• ▸Team strengths & kryptonite: list each member's special ability and weakness
• ▸Work division: assign tasks to draw on each person's strengths
• ▸Check-in ritual: the personal question you'll open each meeting with
• ▸Meritocracy commitment: how ideas get fair consideration across hierarchy
• ▸Risky-conversation norm: how you'll surface conflict instead of avoiding it
• ▸Judgment rule: state that you evaluate idea quality, not polish
• ▸Personal advisory board: names and meeting cadence of your standing sounding board
• ▸Network audit: supporters to seek out and negativity defaults to avoid
• ▸Practice rep: the low-stakes creative action you'll repeat this week

1. 1Locate yourself on the diminisher-multiplier continuum: audit whether your controlling habits underutilize your team's creative talent, or whether you routinely help people produce results beyond what they knew they could do. Liz Wiseman's research across 150+ leaders shows multipliers roughly double a team's output while improving morale.
2. 2Become a talent magnet: identify, attract, and retain the most creative people, then actively help each reach their highest potential rather than hoarding the credit or the interesting problems.
3. 3Set a worthy challenge, not a soft one—define a goal ambitious enough that people don't yet know they can hit it, the way Jobs used his 'reality distortion field' to convince people they could do the impossible.
4. 4Encourage genuine debate: draw out insight from every department—customer service to finance—because no single executive or division holds a monopoly on new ideas.
5. 5Give ownership: hand people real responsibility for outcomes so they exercise their own judgment, rather than exercising tight top-down control over every move.
6. 6Provide 'soft landings' for career risk: create conditions where managers who take sensible risks in unproven areas aren't punished for failure, so fear of failure stops transfixing the team.
7. 7Nurture, don't dictate: supply the 'heat, light, moisture, and nutrients'—the conditions—for a creative culture to grow, since leaders can shape culture but cannot command it into existence.

IDEO's team traveled to Rochester in the mid-1990s and met a Kodak leadership group with deep expertise and George Fisher's agile mind—people who intellectually understood photography's future was digital. Kodak had even invented the digital camera in 1975 and pioneered the first megapixel sensor, a first-mover head start that should have produced lasting advantage. But leadership failed as multipliers on one specific dimension: they did not provide enough 'soft landings' for managers willing to take career risks in digital ventures. With no protection against downside, fear of failure transfixed the team and they clung to the chemistry-based business, underinvesting in digital. This is the knowing-doing gap Sutton and Pfeffer describe—knowledge was abundant, but insight never turned into effective action. A multiplier in that room would have set the digital challenge as worthy, given ownership of it to risk-takers, and absorbed the career risk so people could act; instead a diminisher's climate let one of America's most powerful brands lose its way.

• If you find yourself tightly controlling every decision, then you are diminishing—delegate ownership and measure whether output and morale rise.
• If a goal is one your team already knows they can hit, then it is not yet a worthy challenge—raise it until it stretches beyond their self-assessed limits.
• If people avoid new, risky areas, then check whether you've built 'soft landings'—if not, add protection against career penalty before expecting risk-taking.
• If ideas only ever come from senior people or one division, then you're not encouraging debate—actively solicit insight from every department, since no division has a monopoly on ideas.
• If you're trying to mandate a creative culture by decree, then stop—you can only nurture conditions, so shift to supplying encouragement, skills, and latitude.

• Confusing charisma or intelligence with multiplying: the tell is a brilliant leader whose team still produces less than their potential because capabilities are never activated.
• Owning all the interesting problems yourself: the tell is that team members feel their efforts don't really matter no matter what they do—the diminisher signature.
• Setting challenges without providing support, or providing support without setting challenges: the tell is either paralysis or complacency instead of extraordinary results.
• Punishing failure while asking for innovation: the tell is that everyone talks about the risky future but no one moves toward it—the knowing-doing gap made visible (Kodak).
• Trying to dictate culture top-down: the tell is a mandated 'innovation initiative' that withers because the growing conditions—latitude, encouragement, debate—were never supplied.

• ▸Continuum position: rate yourself diminisher-to-multiplier (1-5) and cite one behavior as evidence.
• ▸Talent magnet: name your most creative people and one action to help each reach higher potential.
• ▸Worthy challenge: state a goal ambitious enough that the team doesn't yet know they can hit it.
• ▸Debate practice: list which departments' insights you're currently missing and how you'll draw them out.
• ▸Ownership handoff: name one decision or outcome you'll transfer full responsibility for this month.
• ▸Soft landing: describe the specific career protection you offer people who take sensible risks.
• ▸Culture conditions: identify the 'heat/light/nutrients' (encouragement, skills, time) you'll add this quarter.
• ▸Knowing-doing gap check: name one thing the team knows to do but isn't doing, and the fear behind it.

1. 1Cap planning and start acting: interact with potential customers right away rather than perfecting a plan, knowing early experiments may render even the best-laid plans obsolete.
2. 2Generate countless ideas and hold divergent options open—do not become invested in only one. The volume matters: Steelcase built over 200 prototypes across all shapes and sizes for one chair.
3. 3Build 'quick and dirty' prototypes that are concrete enough for people to react to—paper-and-Scotch-tape models, foam shapes, plywood components attached to existing parts—before touching expensive materials.
4. 4Put each prototype in front of real end users and stakeholders for reactions. Steelcase took models to local colleges and asked students and professors to interact with them and give feedback.
5. 5Run iterative learning loops: adapt, iterate, and pivot based on the feedback, advancing only the most promising concepts to the next round of fidelity.
6. 6Escalate fidelity only as you learn—move from rough models to sophisticated full-size versions that look exactly like the real product as release approaches.
7. 7Launch to learn: go live in beta and keep iterating from real-world use rather than waiting for a finished, controlled version.
8. 8Use guided mastery—a series of small successes at gradually increasing challenge—to build the courage to keep experimenting through failure, instead of attempting one giant leap.

When Steelcase set out to reinvent the rigid wooden classroom chair, they minimized upfront planning and maximized action through trial and error. Their design team built over 200 prototypes: early on, small paper-and-Scotch-tape models; later, plywood components attached to pieces of existing chairs; then foam shapes and 3D-printed parts to sense shape and size; and mechanisms prototyped in steel. They took 'experience models' to local colleges so students and professors could interact with them and give feedback, feeding each learning loop back into the design. As release to manufacturing approached, they built full-size models that looked exactly like the real thing. That relentless experimentation produced the Node chair—a swivel seat, adjustable work surface, casters, and tripod base for backpacks. Launched in 2010, it reached 800 schools and universities worldwide, proving the payoff of heightened trial and error over a single perfect plan.

• If you feel yourself getting attached to one idea, then force divergent options and more prototypes—keep it quick and dirty until users have reacted.
• If the need for control is holding you at the planning stage, then leap into action and start interacting with potential customers now, treating early plans as disposable.
• If a prototype is expensive or polished, then it's too early—drop to paper, foam, or tape until the concept has survived real feedback.
• If a challenge feels like one impossible giant leap, then break it into a series of small successes (guided mastery) and raise difficulty gradually.
• If reframing the question opens new avenues (e.g., 'reduce perceived waiting time' vs. 'reduce waiting time'), then prototype against the reframed problem, not the original.

• Staying stuck at the planning stage out of a need for control—the tell is a detailed plan and zero contact with real users or prototypes.
• Falling in love with a single idea too early—the tell is that you're refining one concept instead of exploring a range of divergent options.
• Prototyping at high fidelity from the start—the tell is spending on polished models before anyone has reacted to a rough version.
• Treating failure as a verdict rather than data—the tell is being defensive or embarrassed about trial and error instead of collecting 'war stories' on the path to success.
• Building without putting models in front of end users—the tell is that iterations are driven by internal opinion, not feedback from actual people in context.

• ▸Reframed question: state the problem in a way that opens new avenues (e.g., perceived vs. actual).
• ▸Idea count this round: list the divergent options generated—aim for many, not one.
• ▸Prototype fidelity: name the cheapest form that's concrete enough to react to (tape/foam/plywood/full-size).
• ▸Who reacts: name the real end users/stakeholders who will test it and where.
• ▸Feedback captured: record what users did and said, not what you hoped.
• ▸Adapt / iterate / pivot decision: state what changes for the next loop and why.
• ▸Fidelity escalation trigger: what you must learn before building a more polished version.
• ▸Launch-to-learn plan: how you go live in beta and what you'll measure from real use.
• ▸Failure log: note this round's 'war story' and the lesson kept for the path forward.

1. 1Start the problem-solving process with empathy toward your target audience—kids, colleagues, clients, or consumers—rather than with technical specifications. Watch how people actually experience the current situation.
2. 2Look beyond surface symptoms and the raw facts. Doug looked past scanning speed and resolution to the emotional experience of frightened young patients; find the human dimension competitors are ignoring.
3. 3Prototype a concrete change with the people affected. Gather a cross-functional volunteer group (like the airline task force of pilots, dispatchers, and crew schedulers) and test procedures against the real problem.
4. 4Balance three factors on every innovation: technical feasibility, business viability, and human desirability. Find the overlapping sweet spot rather than starting and stopping at what's technically possible.
5. 5Take the first step into action instead of staying stuck at the planning stage. Belief that you can effect change (Bandura's self-efficacy) precedes the outcome—without it, no first step gets taken.
6. 6Measure the tangible result: faster recovery time, improved test scores, more donors recruited, a case won, a child who wants to come back. Name the specific outcome the intervention produced.
7. 7Give credit and disarm insecurity so the group stays focused on the work and its impact, not on self-promotion or comparison.

Doug at GE competed in a market obsessed with technical specs—scanning speed, resolution—while children were terrified of the MRI machine. Instead of fighting that specifications battle, he approached the challenge from the patient's human perspective and redesigned the experience into an MRI 'pirate ship.' The measurable, human outcome came when a six-year-old girl who had just been scanned tugged her mother's skirt and asked, 'Mommy, can we come back tomorrow?' That single question told him the intervention had changed how young patients experienced the machine. Less than a year after his epiphany, his increased creative confidence moved him into a new role as a thought leader at GE. The story shows how starting with empathy, not technical factors, produced a breakthrough that positively impacted patients and their families.

• If competitors are locked in a battle over technical specifications, then shift the ground to human desirability where new opportunities for change are richest.
• If a project is stalled at the planning stage from a need for control, then leap into a prototype and become comfortable with uncertainty.
• If people can't articulate a tangible outcome (faster recovery, higher scores, a patient who wants to return), then the work hasn't yet produced impact—keep going.
• If an idea passes technical feasibility but no one wants it, then it fails the desirability test and won't create real-world impact.
• If team members are self-promoting instead of focusing on the work, then disarm the insecurity early, give credit, and refocus on outcomes.

• Starting and stopping at feasibility. Clients presented IDEO with thousands of new technologies; the tell is a pile of clever tech with no human problem it solves.
• Executive lip service (Mauro Porcini's 'hidden rejection' phase). One sponsor pushes a method, others pay lip service and never commit—the tell is the knowing-doing gap where words substitute for action.
• Chasing the specifications war. The tell is measuring success only by speed/resolution while ignoring how the person on the receiving end feels.
• Getting sidetracked by comparison and insecurity. The tell is people boosting themselves through self-promotion instead of feeling good about what they produce.
• Believing you must switch careers, quit, or move to Silicon Valley to have impact. The tell is waiting for the 'right' setting instead of applying creativity to the work you already do.

• ▸Audience: name the specific people you're designing for (kids, colleagues, patients).
• ▸Surface symptom vs. human need: what everyone treats as the problem vs. what people actually feel.
• ▸Feasibility: the technical factor that must work.
• ▸Viability: why this makes business sense.
• ▸Desirability: the human reason people will want it.
• ▸First action/prototype: the smallest concrete step you can test this week.
• ▸Cross-functional testers: who joins the volunteer task force.
• ▸Tangible outcome metric: the number or moment that proves impact (e.g., 40% faster recovery, 'can we come back tomorrow?').

1. 1Run a daily self-audit: at the end of each day, ask yourself 'When was I at my best?' or 'When was work most rewarding?' and record the answer, as David did by scoring his days up or down.
2. 2Track the pattern, not the anecdote. Use a mood-mapping app, stickers in an appointment book, or a simple up/down score to log daily highs and lows until surprising patterns emerge (David found solitary studio hours plus his favorite music raised his scores).
3. 3Name the specific activities that raise your score and those that drag it down—be granular (making a metal bracelet, blasting music, helping others) rather than vague ('work' or 'weekends').
4. 4Gravitate deliberately: schedule more of the score-raising activities and cut the score-lowering ones. This is behavior change, not just insight.
5. 5Diagnose the 'curse of competence'—separate what you can do well from what actually fulfills you. Ask whether you gain real fulfillment or are merely 'resigned' to a role you can perform.
6. 6Start passion-testing before you quit anything: use side projects and free time (a weekend piano habit, Lego robots with your kids, a d.school Bootcamp class) to sample new directions with low stakes.
7. 7Convert insight into action—creative confidence only pays off when you're brave enough to act on ideas. Take the first concrete step, accepting the cost, once the pattern is clear.

Jeremy Utley excelled at analysis and, on the advice of career counselors, took a well-paid financial analysis job by his mid-twenties—the 'curse of competence.' He could do the work but gained no real fulfillment, showing up 'resigned to the fact that I would hate whatever I did for the next twenty years.' Sent by his firm to get an MBA at Stanford's GSB, he enrolled in a d.school Bootcamp class as a diversion and initially wrote it off as 'playtime.' Halfway through he realized it was as rigorous as anything he'd done but far more rewarding, as he struggled to grapple with ambiguity and prototype ideas. Torn between his old mindset and the new one, he ultimately left the tempting salary and status—even repaying two years of tuition—because he'd had a genuine experience and 'felt like I needed to pursue the new path.' He stayed at the d.school as a Fellow, trading competence-without-fulfillment for engaged, meaningful work.

• If you can perform a role well but gain no real fulfillment from it, then you're caught in the 'curse of competence'—treat competence as insufficient evidence you're in the right place.
• If a day scores higher, then identify the specific activity that raised it and schedule more of it; if it scores lower, then reduce or avoid that activity.
• If you believe you can effect change (self-efficacy), then set your sights higher and persevere—Bandura's research shows belief drives action, so build the belief through early wins.
• If an idea excites you but you're stuck at the planning stage from a need for control, then leap into action and get comfortable with uncertainty rather than waiting for certainty.
• If pursuing fulfillment carries a real cost (lost salary, repaid tuition), then decide based on whether staying means resigning yourself to the status quo—that resignation is itself the warning.

• Equating creativity with artistic talent and concluding fulfilling creative work isn't for you—the tell is thinking 'CEOs, lawyers, and doctors aren't paid to be creative' or 'either you're born with it or not.'
• Mistaking rigor for drudgery and dismissing rewarding work as 'playtime'—the tell is Jeremy's early write-off of Bootcamp before realizing it was as demanding as his hardest past work.
• Staying stuck in analysis and planning because of a need for control—the tell is never leaping into action, letting the fear of failure paralyze you.
• Doing the tracking but never changing behavior—the tell is logging your moods yet keeping the same routines, so insight never becomes epiphany plus behavior change.
• Waiting for external permission or 'concrete evidence' you're allowed to be creative (a parent who danced or built things)—the tell is rationalizing your own spark instead of acting on it.

• ▸Date: the day you're logging
• ▸When was I at my best today?: one specific moment or activity
• ▸Day score (up / neutral / down): your overall rating
• ▸Score-raising activity: the specific thing that lifted you (be granular)
• ▸Score-lowering activity: the specific thing that dragged you down
• ▸Curse-of-competence check: was I doing what I'm good at but not fulfilled by? (yes/no)
• ▸More-of-this next week: one score-raiser to schedule deliberately
• ▸Side project to test: one low-stakes experiment in free time to try a new direction
• ▸First brave action: the one concrete step you'll take on an idea this week

1. 1Start in the field, not at your desk: go where the human uses the thing and watch a real interaction. Doug Dietz saw his MRI installed and only understood the problem when a frail young girl walked toward the machine — inspiration comes from observation, not from asking whether people 'liked the new features.'
2. 2Kill the leading-question habit. Doug called his own hospital conversation 'a perfect example of bad interviewing technique.' Ask open questions and watch behavior instead of fishing for confirmation you did a good job.
3. 3Synthesize what you observe into a human need before you generate solutions. The insight for Doug was not 'the machine works'; it was 'children are terrified of this experience' — reframe the problem around the person.
4. 4Ideate against that need using divergent, non-analytical modes (the 'fuzzy or unconventional' exercises like improv the d.school runs), and resist the instinct to bolt for a 'really important phone call' when it feels uncomfortable.
5. 5Prototype and test in the real setting rather than planning to certainty. The airline task force of pilots, dispatchers, and crew schedulers prototyped weather-disruption procedures — action over the planning stage where the need for control traps people.
6. 6Balance the three lenses on any surviving idea: desirability (does it meet a real human need you observed), feasibility (can it be built), and viability (does it sustain). A design-award-winning MRI passed feasibility and viability but failed desirability for its youngest patients.
7. 7Iterate on early success. The methodology works because 'that early success shakes up how they see themselves' — ship a small win, let it rebuild confidence, then take on the bigger version of the problem.

Doug Dietz, a 24-year GE Healthcare veteran, spent two and a half years designing an MRI system that was submitted for an International Design Excellence Award. Standing next to the installed machine, he asked the technician how she liked its new features — bad interviewing technique, because it sought praise rather than truth. Then he stepped into the hall and saw a frail young girl walking toward his machine, tightly holding on, terrified. That single observation reframed the problem: the device was a triumph of feasibility and viability but a failure of desirability for the children who had to enter it. The insight — the human experience, not the hardware, was broken — is exactly the synthesis step design thinking demands. It shows why inspiration must come from watching a real person in the real setting, not from your own satisfaction with the build.

• If you catch yourself asking whether people 'like' what you made, then stop — you are seeking confirmation, not insight; switch to open observation.
• If an idea wins on design/build but you have not watched the actual end user, then treat desirability as unverified and go observe before proceeding.
• If the team stalls at planning because someone needs control and certainty, then force a low-cost prototype into the real environment to convert doubt into evidence.
• If someone reaches for their smartphone the moment an exercise gets 'fuzzy or unconventional,' then that is insecurity, not a real interruption — hold them in the discomfort a while longer.
• If you are tempted to teach creativity from scratch, then reframe: people already have it, so your job is to recapture it with new skills and mindsets.

• Leading interviews that fish for validation — the tell is questions phrased as 'how do you like…' and the interviewer 'prepared to come away patting himself on the back.'
• Optimizing for expert approval over the real user — the tell is chasing the 'Oscars of design' award while the frail child in the hallway is terrified of the object.
• Getting stuck at the planning stage from a need for control — the tell is endless refinement with no prototype ever placed in front of a real person.
• Escaping discomfort during divergent work — the tell is people whipping out smartphones and heading for the exits to make 'really important' phone calls during improv or open-ended exercises.
• Declaring yourself the wrong 'type' — the tell is the phrase 'I'm just not the creative type,' a defense triggered by insecurity in an unfamiliar setting.

• ▸Real setting observed: where did you watch the actual user, not a proxy?
• ▸User behavior seen: what did the person do (not say) that surprised you?
• ▸Human need synthesized: state the need in one sentence about the person, not the product
• ▸Desirability: what evidence shows this meets that observed need?
• ▸Feasibility: can it actually be built with what you have?
• ▸Viability: does it sustain over time / pay for itself?
• ▸Weakest lens: which of the three is unverified right now?
• ▸Next prototype: the smallest thing you can put in front of a real user this week

1. 1Diagnose the false belief first. Name the specific fear or fixed-mindset story blocking the person ('I'm not the creative type'), because guided mastery works by replacing false beliefs with firsthand experience, not argument.
2. 2Break the intimidating goal into a graduated sequence of manageable steps, each only slightly harder than the last—the way Bandura moves someone from watching a snake, to standing at the open door, to standing there with him, to touching it.
3. 3Set the first challenge small and quick enough that success is nearly assured: a fast design challenge like redesigning the gift-giving experience or rethinking a daily commute.
4. 4Let people solve it themselves; supply only a small nudge or 'stand at the door with them' when a step is too scary. Ownership of the small win is what shifts the belief system.
5. 5Debrief the success explicitly. Ask whether the new result beat their initial cliché answer—make them see, in their own case, that effort and method expanded their capability.
6. 6Run many short cycles rather than one big project, maximizing the number of learning cycles so each success bootstraps confidence for the next, harder step.
7. 7Assign a coach or catalyst to guide the progression—someone knowledgeable in the field, as Bandura was with the snake, or Intuit's 'Innovation Catalysts.' Show, don't tell.
8. 8Increase the challenge level only after each small success lands, so the next goal is effortful but never completely out of reach.

Doug at GE couldn't launch a full R&D project to redesign the MRI machine, so he shrank the goal to redesigning the experience—a manageable first step. He started with the lowest-risk action: observing children at a day care center and talking to child life specialists to build empathy. He then pulled together an ad hoc team (GE volunteers, a children's museum, two hospitals' doctors and staff) and built a single prototype rather than a grand system. Making no changes to the complex scanner technology, he applied colorful decals and wrote an operator script turning the MRI suite into a pirate-ship adventure, then installed it as a pilot at the University of Pittsburgh Medical Center. Each modest step—empathy, prototype, pilot—succeeded and justified the next. The cumulative small wins let him accomplish, incrementally, what would have been impossible as one giant leap.

• If a step provokes too much fear to attempt, then make it smaller or offer to do it alongside them ('stand at the door with them') rather than pushing them through it alone.
• If someone insists 'I'm just not the creative type,' then don't argue—engineer a firsthand small success, because direct experience, not persuasion, dispels the false belief.
• If you must choose between one big project and several short ones, then choose the short ones to maximize learning cycles and the number of confidence-building wins.
• If a person completes a challenge, then debrief it so they consciously register that they outperformed their initial answer—an unexamined win builds less belief.
• If you're rolling this out in an organization, then build creative confidence one key player at a time through practice and coaching, not top-down executive mandate.

• Telling instead of showing: a CEO orders 'boost innovation' and employees just add a user slide to check a box, never experiencing the method—the tell is compliance without belief.
• Starting too big: framing the first task as the intimidating end goal, so people freeze or fail hard enough to confirm their fear instead of building courage.
• Solving it for them: jumping in with the full answer removes the firsthand success that changes the belief system—the tell is that the coach, not the learner, owns the win.
• Skipping the debrief: people succeed but never consciously compare the outcome to their initial cliché answer, so the mindset shift doesn't register.
• Running one long project: few learning cycles means fewer small successes, so confidence never compounds—the tell is enthusiasm that fades before mastery accrues.

• ▸Intimidating goal: the creative outcome that currently feels out of reach
• ▸Blocking belief: the exact fixed-mindset story to dispel ('I'm not good at...')
• ▸Step 1 (near-certain win): the smallest quick challenge you can nearly guarantee succeeds
• ▸Steps 2–5 (graduated): each next challenge, slightly harder, effortful but not out of reach
• ▸Coach support per step: where you'll give a nudge or 'stand at the door with them'
• ▸Ownership check: confirm the learner, not you, produces the solution at each step
• ▸Debrief question: 'Was this better than your initial answer?'—asked after each win
• ▸Cycle count: number of short projects planned to maximize learning cycles
• ▸Next-level trigger: the success signal that permits raising the challenge

1. 1Pick the population you're designing for and go to where they already are — a day care center, an operating room, an airport security line — rather than pulling them into a conference room. Doug started by observing young children at a day care, not by surveying parents.
2. 2Observe behavior in natural context before you ask anything. Watch for points of frustration and moments of clumsy improvisation. When redesigning a can opener, you watch elderly people actually use it to spot where they struggle.
3. 3Talk to unexpected experts around the user, not just the obvious authority. Doug consulted child life specialists and children's museum staff; in health care, talk to the medical assistant, not only the doctor.
4. 4Seek out extreme users and early adopters to see the range of behavior — how people improvise workarounds reveals latent needs the average user can't articulate.
5. 5Push past stated needs to motivations and core beliefs: ask why people do what they currently do, aiming to understand what makes them feel safe or frustrated. Doug worked to understand how children perceive an MRI machine and what makes them feel safe in a new experience.
6. 6Build first-person empathy by putting yourself in the user's position — wash clothes by hand in their sink, stand beside the surgeon, calm the agitated passenger — so you never forget you're designing for real people.
7. 7Move up the difficulty ladder if venturing to customers feels scary: start as a fly on the wall in an online forum hunting for pain points, then try your own customer service, then interview unexpected experts, then play detective in a real space.

Doug, a GE engineer, felt responsible for MRI machines that terrified the pediatric patients they served. Instead of launching an R&D project to redesign the scanner's technology, he redesigned the experience by starting with empathy. He observed and gained empathy for young children at a day care center, talked to child life specialists to understand what pediatric patients went through, and pulled in doctors, hospital staff, and experts from a local children's museum. Because GE's machines already had strong technical and business viability, he focused entirely on the human factor: how children perceive the machine and what makes them feel safe. That empathy produced the 'Adventure Series' — colorful decals turning the MRI suite into a pirate ship, with a wooden captain's wheel around the chamber opening that also made the small circumference feel less claustrophobic, plus a script for operators to narrate the adventure. Making no changes to the technology inside, his empathy for young patients led to a breakthrough that assured the product's success.

• If the technology and business case are already solid (as with GE's MRI machines), then start with human factors — that's where the untapped opportunity sits.
• If you find yourself asking 'how might we reduce customer waiting time,' then reframe to 'how might we reduce perceived waiting time' — empathy about how people feel opens avenues that solving the literal problem does not.
• If you can only observe behavior but not motivation, then go deeper — get at why people do what they do and their core beliefs before you design.
• If you're afraid to approach real users, then start at the easiest rung (a fly on the wall in an online forum) and climb toward live interviews.
• If the obvious authority gives you polished answers, then go to the unexpected expert — the receptionist, the repair person, the medical assistant — who sees the real friction.

• Competing on technical specs instead of human needs — Doug's competitors fought endlessly over scanning speed and resolution while missing the terror of the patient. Tell: your improvement plan is a list of features, not a list of people's experiences.
• Stopping at observed behavior and never reaching motivation. Tell: you can describe what users do but can't say why they do it or what makes them feel safe.
• Taking stated needs at face value and searching forums for feature evaluations rather than pain points and latent needs. Tell: your notes are full of requests, empty of unmet needs.
• Skipping synthesis — collecting stories but never moving from concrete observations to abstract truths that span groups. Tell: you have a pile of anecdotes and no reframed problem or actionable principle.
• Avoiding the field because venturing onto users' turf feels uncomfortable, so you rely on assumptions. Tell: you're theorizing from your desk and heading for the exit when the work gets fuzzy.

• ▸User & context: who you're observing and where they naturally are
• ▸Observed behavior: what they actually do, especially frustrations and workarounds
• ▸Extreme user note: how an early adopter or power user improvises differently
• ▸Unexpected expert: the non-obvious person you talked to and what they revealed
• ▸Stated need: what the user says they want
• ▸Latent need: the deeper motivation or 'feel safe' factor beneath the stated one
• ▸First-person insight: what you learned by doing the task yourself
• ▸Reframed question: your 'how might we...' rewritten from the human angle
• ▸Fertile ground: the theme or focus area you'll take into ideation

1. 1Split the work into many quick cycles rather than one big deliverable — the Kelleys deliberately assign 'multiple quick design projects rather than one big project, to maximize the number of learning cycles.' Decide how many cycles you can run in the time you have and shrink each accordingly.
2. 2Set a tight design challenge that forces immediate output (e.g., 'redesign the gift-giving experience' or 'rethink your daily commute'), then start building instead of researching.
3. 3Get out of the planning stage the moment you feel the need for control taking over — treat 'comfortable with uncertainty' as the signal you're ready to move, not full information.
4. 4Prototype with whatever is fastest and roughest; the Node chair team built physical models progressively toward ones 'that looked exactly like the real thing,' but only after cheaper, faster iterations.
5. 5Use guided small successes: attempt something manageable, complete it, let that success make you 'eager to do more,' then raise the difficulty on the next cycle.
6. 6Go observe the real user in their real context before deciding you're done — Doug only saw the failure of his MRI when he stood in the hallway and watched a scared child, not while admiring specs.
7. 7After each cycle, extract the learning explicitly and feed it into the next attempt; treat every experience 'as an opportunity they can learn from' rather than a verdict.
8. 8Don't be defensive about trial and error — collect the 'war stories' of failures as evidence of a working method, the way Edison and the Wright brothers did.

Doug spent two and a half years engineering an MRI machine and was ready to accept a design award for it. Only when he stepped into the hospital hallway and watched a frail, crying young girl being walked toward his machine — and saw the technician reach for the phone to call an anesthesiologist — did he learn that as many as 80 percent of pediatric patients must be sedated to lie still. That moment turned pride into a sense of failure and reframed the problem: not scanning speed or resolution, but a child's terror of a 'big scary machine you have to go inside.' Rather than re-plan for years, Doug acted on the new insight, redesigning the patient experience. Less than a year after that epiphany the change was real enough that a young patient tugged her mother's skirt and asked, 'Mommy, can we come back tomorrow?' That single question made his effort worthwhile and catapulted him into a thought-leader role at GE — the payoff of acting quickly on a lived observation instead of defending the finished design.

• If you feel the need for control keeping you at the planning stage, then stop planning and ship a rough prototype — control-seeking is the tell you're stalling.
• If a challenge feels too big to attempt in one leap, then break it into a series of small successes and do the first one now.
• If you're about to defend or hide a failed attempt, then log it as a war story and start the next cycle — trial and error is the method, not a mistake.
• If you're optimizing specs your competitors also chase (speed, resolution), then go observe the actual human using the thing to find the untouched opportunity.
• If you have limited time, then choose more short learning cycles over one long project to maximize learning per unit of effort.

• Confusing thought with action: coming up with ideas but never being 'brave enough to act on those ideas' — the tell is a full idea list and zero prototypes.
• Staying stuck at the planning stage out of a need for control — the tell is demanding more certainty or data before you'll start.
• Admiring your own output instead of testing it (Doug 'prepared to come away patting himself on the back') — the tell is you haven't watched a real user touch it.
• Betting everything on one big project — the tell is a single long timeline with no intermediate learning cycles.
• Treating failure as identity ('I'm just not the creative type') rather than a cycle to learn from — the tell is defensiveness or embarrassment about trial and error.

• ▸Tight challenge: state the problem as a quick, doable design challenge
• ▸First observable step: the smallest thing you can build or try today
• ▸Time box: hours/days for this single cycle (keep it short)
• ▸Prototype form: the fastest, roughest way to make the idea tangible
• ▸Real user + context: whose behavior you'll watch, and where
• ▸Success signal: the small win that tells you the cycle worked
• ▸Learning captured: one thing this cycle taught you
• ▸Next cycle: how you raise the difficulty or change based on the learning

1. 1Name the fixed-mindset belief you currently hold out loud: catch the exact phrasing, e.g. 'I'm just not the creative type' or 'I'm not good at that kind of thing.' You cannot let go of a belief you haven't articulated.
2. 2Reframe capability as unknown, not deficient. Replace 'I can't do X' with Dweck's premise: your true potential is unknown and unknowable, and cannot be foreseen without years of passion, toil, and training.
3. 3Identify which of the two voices you're listening to in a given moment. The fixed voice whispers 'why embarrass ourselves now?'; the growth voice whispers 'effort is the path to mastery, so let's at least give this a try.' Consciously choose the second.
4. 4Take the course you'd otherwise avoid. When offered a chance to improve a weak area (the Hong Kong 'remedial English' test), say an emphatic yes rather than protecting your image—declining is sabotaging your long-term success to hide a weakness.
5. 5Stay with the methodology past the fuzzy, uncomfortable point. When an improv or open-ended exercise triggers the urge to 'whip out your smartphone' and exit, treat that impulse as the tell of insecurity, not a real interruption—remain and let a small amount of practice renew the capacity.
6. 6Treat creative capacity as a muscle: schedule repeated low-stakes reps with encouragement, because imagination, curiosity, and courage return quickly 'with just a small amount of practice.'
7. 7Set your sights higher after each small win, following Bandura's self-efficacy loop—belief that you can effect change makes you try harder, persevere longer, and recover faster from failure.

At the d.school, David and colleagues start with a coffee-related design brief and deliberately ask students to set aside their initial, cliché answers—the ones already in their heads. Students dig deeper and observe people's actual behavior around coffee drinking to find latent needs. Working in a collaborative environment, they generate dozens of ideas, from a coffeepot that knows exactly how hot you like your drink and delivers it that way every time, to an automatic stirrer you drop into your cup. The professors then ask whether any of these new solutions beat their first answers; usually the answer is yes. That yes is the growth mindset made concrete: capability wasn't fixed at the level of the first idea—it expanded through effort and observation. The founders expected to teach 'analytical types' to be creative, but found everyone already had creativity 'in spades'; the real job was helping them recapture it by adopting new mindsets.

• If you hear yourself say 'I'm not the creative type,' then treat it as the creativity myth, not a fact, and proceed anyway—everybody is the creative type.
• If you're offered a course or exercise that would expose a current weakness, then say yes; declining to protect your image turns 'limited ability' into a self-fulfilling hypothesis.
• If a task feels fuzzy, unconventional, or uncomfortable and you feel the urge to leave for a 'really important' phone call, then stay—the discomfort is insecurity, and the breakthrough sits on the far side of it.
• If your first answer is the obvious, cliché one, then set it aside and dig deeper; the best ideas rarely arrive first.
• If both voices are whispering, then listen to the one saying effort is the path to mastery, because in reality we all carry a bit of both mindsets and the choice is yours.

• Assuming creativity is a fixed trait 'like having brown eyes.' The tell: you sort people (and yourself) into born-creative vs. not, and stop trying before the reps begin.
• Guarding your comfort zone to avoid revealing your limits to others. The tell: you decline help, courses, or exercises that might expose a weakness—the Hong Kong fixed-mindset 'not very interested' response.
• Bolting at the first uncomfortable moment. The tell: smartphones come out and people head for the exits the instant an exercise turns unconventional.
• Stopping at your initial idea. The tell: you defend the first, cliché answer instead of observing behavior and iterating toward deeper latent needs.
• Expecting to grow without practice or encouragement. The tell: you conclude 'I'm just not good at that' after one attempt, ignoring that the capacity returns with a small amount of guided repetition.

• ▸Fixed belief I'm holding: write the exact self-talk phrase, e.g. 'I'm not good at that kind of thing.'
• ▸Trigger situation: the specific fuzzy/uncomfortable task where that voice appears.
• ▸Growth reframe: rewrite the belief as 'my potential here is unknown and expandable through effort.'
• ▸Avoidance move I default to: name your version of 'whipping out the smartphone.'
• ▸Emphatic-yes action: the course/exercise/rep you'll say yes to despite exposed weakness.
• ▸One small rep this week: a low-stakes practice attempt with a supportive setting.
• ▸Evidence of expansion: what result would show the capability grew (e.g. a later idea beating my first)?
• ▸Which voice I chose: fixed ('why embarrass ourselves') or growth ('let's at least give this a try').