Coaching practices for We're Heading Into a Project Nobody Has Done Before but My Team is Treating it Like a Checklist Where Any Slip is Failure So They're Hiding the Dead Ends Instead of Telling Me What They're Finding Out

Describe almost anything you are working through and IX Coach finds the practices whose real-world fit is closest. For We're Heading Into a Project Nobody Has Done Before but My Team is Treating it Like a Checklist Where Any Slip is Failure So They're Hiding the Dead Ends Instead of Telling Me What They're Finding Out, these are the strongest matches in the current practice library.

Does this sound like the set of challenges you might be facing?

  • We’re heading into a project nobody has done before, but my team is treating it like a checklist where any slip is failure
  • We’re about to kick this off and everyone’s upbeat, but I have a quiet feeling there are ways this falls apart that nobody wants to say out loud while we’re all still excited.
  • I’m about to commit to this timeline and on paper it all looks fine, but I have a nagging feeling I’m glossing over the ways it could go sideways because admitting them now feels like talking myself out of it before I’ve even started.
  • We did the exercise where we imagined it failing and listed why, but I have a nagging sense the most likely way this actually goes wrong is something nobody was willing to say out loud in the room
  • Whenever my team sits down to spot risks, the most senior or loudest person says the first thing and suddenly everyone’s nodding along to the same two concerns

Practices that may help

  1. Frame uncertain work as learning
    Before starting a challenging project, name it explicitly as an experiment where mistakes generate information.
    Psychological Safety in Teams
  2. Run a pre-mortem before you start
    Before a project begins, ask: assume it failed — what went wrong?
    Hindsight Bias: Why Everything Seems Obvious in Retrospect
  3. Run a premortem before committing
    Imagine the project has already failed and work backwards to find why.
    The Planning Fallacy — Why Your Estimates Are Always Wrong
  4. Combine the pre-mortem with red team pressure
    Run a pre-mortem and then ask the red team to find the failure mode the team missed.
    Red Teaming: Stress-Testing Plans Before They Fail
  5. Write reasons independently before discussing
    Everyone records failure causes alone first, so the room doesn’t converge too soon.
    The Pre-Mortem: Imagine It Already Failed
  6. Use feedforward to align team members on goals before projects begin
    At the start of a project, invite feedforward on how to succeed — before any performance to critique.
    Feedforward: Future-Focused Feedback That Actually Changes Behavior
  7. Run a pre-mortem before committing to a plan
    Imagine the plan has already failed and ask what went wrong.
    Confirmation Bias: Seeing What You Expect to See
  8. Run a pre-mortem from the outside-view perspective
    Imagine the project has failed — then ask which base-rate failure type caused it.
    The Outside View
  9. The premortem (imagine the project already failed)
    Before starting, assume the plan has already failed and ask why — then fix it now.
    Premeditatio Malorum, in Depth
  10. Frame the work as a learning problem, not an execution problem
    Name the uncertainty and interdependence out loud so people expect to learn, not just deliver.
    Psychological Safety, Made Practical

Related concerns

Describe your situation in your own words to search the complete practice library.

Practice this with IX Coach

Try this practice