Our approach and methodology

Understand the proposed approach to technical decisions, relevant CTO experience and the responsibilities to agree before proceeding.

Bring us your case

Tell the curator which decision you face, what your team has tried and what remains uncertain, so the conversation starts with your actual constraints.

Pick a time

Before, during and after a discussion

  1. Frame the decision and constraints

    Describe the milestone, current ownership and unresolved choice using nonconfidential context, so a proposed discussion starts with a concrete decision rather than a general request.

  2. Discuss relevant experience and scope

    Explore which project or leadership experience relates to the decision and agree participation, conflicts and information boundaries before treating a proposed contribution as confirmed.

  3. Examine the evidence and alternatives

    Within an agreed scope, separate observations, assumptions and alternatives; the decision and any required domain acceptance remain with the named owners.

  4. Agree responsibility for the next step

    Record what remains unknown, what the next decision requires and who accepts it, without assuming a written artifact, implementation mandate or standard follow-up.

What to agree as a useful outcome

Explore the Private Club
  • The technical decision and the evidence that would change it
  • Options compared with their assumptions and remaining evidence gaps
  • Responsibilities separated between adviser, implementation team and acceptance owner
  • A bounded next step rather than an assumed delivery commitment
FAQ

Straight answers