Behaviors That Stick
Practice: The Input Ask

Ask one real question before you finalize, so the work gets better before it ships.

The Hook

Before you finalize, ask one person one real question. Not for approval — but because their perspective makes the work better.

DefaultBehavior SpectrumEmbedded
01
SIGNAL

When does this matter?

Before any piece of work leaves your hands that will be acted on, built from, or evaluated by someone who wasn't part of creating it.

You're about to send the project brief to the team that'll build from it — no one else has seen it yet.
02
REDIRECT

What do I do?

Identify one person whose work touches yours. Ask one specific question — not 'does this look right?' — targeting your least-certain part.

You ask the engineer: “Does the timeline in section 3 account for the QA handoff?” She flags a gap you'd missed.
03
SHIFT

How will I know it's working?

You'll know it's clicking when you start hearing “you always think of everything” from the people who receive your work.

Your manager forwards your brief with one line: “This is thorough — nothing to add.”
04
EMBEDDED

How do I know it worked?

Your work lands with fewer surprises and fewer revision rounds. People you ask start to feel their perspective is valued.

The engineer starts looping you in on her drafts before you even ask — she expects you'll do the same.
↺ Repeat until Embedded
Before (Old Pattern)
After (Embedded)
  • You finalize and send.
  • Gaps surface later, as revisions or surprises.
  • You ask one person one real question first.
  • The gap is caught before it ever leaves your hands.
The Goal

Catch what you can't see alone, before the work leaves your hands.