The First 30 Days
This is a tool to see how my ways of working will meet with your specific needs. Download or copy the .md file, load it into your AI tool of choice and prompt it with your questions or the ones suggested here.
Plain text, ready to paste into Claude, ChatGPT or Gemini.The full agreement Prefer to read it yourself? Everything in the .md file, on one page. Read it here +Hide the agreement −
What we're agreeing to
Our first 30 days set the pattern for everything after. This document sets the foundation for our working agreement: what each of us commits to, how we'll communicate and decide, and what we'll do when things change. It's a starting point, not a fixed plan. We'll adjust it together as I assess the problem, the team and the organization as a whole.
Value that keeps compounding after I leave. By day 30, your team is deciding with evidence, with one change underway that they own.
Before day one
We'll hold a scoping conversation and agree, in writing, on:
- The friction we're here to address, in your words
- A sponsor who owns the outcome and can make decisions
- The people, data and systems I'll have access to
- The history and context behind the problem, not just the org chart
- What would have to change for this to be worth it
- How we'll meet: a weekly check-in with the sponsor, and where day-to-day conversation happens
How we'll define success
Before the work starts, we agree on what success looks like. This is the picture I'll hold us both to: value that keeps compounding after I leave or move onto a different focus.
Success looks like
- The people I work with have the confidence to put what we built together into practice, without needing me in the room
- Teams decide with evidence, ship, and learn from the results
- People say what they think without fear that they will be sidelined afterwards
- Skills development changes how people work on Monday, not just how they feel on Friday
- The foundation holds: clean data and clear roles before the shiny thing
- What we learned ends up somewhere other people can use
- Teams share a common toolkit, and the judgment to adapt it or set it aside when the problem calls for it
- Can they make this call without me?
- Are people thinking about their teams and process as products to always reflect on for improvements?
- What changed from my involvement?
Thinking and making decisions
These are the lenses we'll use to look at problems together. Which one leads depends on the problem.
How we'll get to a decision
- Gather inputs from the people who have to live with the call
- The deciding question is always: which option creates the most value?
- When the evidence points in a strong direction and supports a solid hypothesis, not when it's complete
- Name what we're giving up before we commit
- Easy-to-undo calls get made fast. Hard-to-undo calls get a baseline and roadmap
- New evidence reopens a decision. New opinions don't
Communication
We set these standards in our first week, so we never have to negotiate them in the middle of the work.
My style: Plain, warm, direct. Blunt when something is actually harmful. Kindness always. Witty sometimes.
Philosophy: Good work depends on honest communication, in both directions. These are the standards I hold myself to, and the ones I'll ask you to hold me to.
What you can expect from me
- Framing of the data. My honest reflection and insights on what it means
- The voice of real users and real quotes, connected to solutions, always attributed
- Harm named plainly. If fear is shaping how people work, I'll say so
- The conclusion is an accounting of what comes next: next steps, recommendations, opportunities, open questions to answer
- Humour as part of the culture. Hard work goes better when a team can laugh together, never at each other
- Joy and passion, because I love the work I get to do
What I'll expect from you
- Transparency trumps all else. I can't make the best decisions if I don't have all the info
- Bring the data and your read on it. What did you see, and what do you think it means?
- Start with curiosity
- Radical candor. Care about the person, and care about them improving
- When calling out a friction point, focus on systems and processes. Blaming a person only causes future problems to be hidden
- Close every conversation with what comes next and who owns it
- Pass on what you learn so the whole team gets sharper
- Disagree in the room, not in the hallway
Where we'll talk
We'll agree up front which channel is for what.
How we'll give and take feedback
- Direct about the work, kind to the person
- I start with a question before I give an answer
- I'll point out the gap, and help you close it
- I name the system first, then the part each person owns
- Never no, always not yet. Bring evidence and a deprioritized idea moves up
- Feedback is data. The sooner I have it, the sooner I can act on it
- Be specific: what happened, and what it meant for you
- Show me the evidence. I'll change my mind
- I'll act on it, and tell you what changed
What to know going in
A few things are true about how I work. Better you hear them now than discover them in week two.
I ask a lot of questions. It's how I map the system before I touch it
I'll say what others in the room won't. Kindly, but I'll say it
I'm a generalist by choice. I bring fresh eyes, ask the naive questions everyone else stopped asking, and I'm willing to disrupt how things have always been done. I'll tell you when something is outside my lane
I care about the people as much as the product. When the culture is hurting the work, I name it
I'd rather you need me less over time. That's how I know it worked
How we'll work together
What working together looks like
- I start by mapping the system: people, process, product and data
- I make the full picture visible: what we're building and how we're building it
- I help my clients structure goals that are clear and measurable
- I validate a baseline early, so we can track what changed
- I work alongside the team, not above it
- I share what I'm seeing as I see it, including the messy parts
- I build a culture of reflection, so the learning outlives the meeting
- What's the friction?
- What did I see, hear or measure?
- What do I recommend, and what are we giving up?
- Who else needs to be part of this call?
What I'll ask
Where we'll point the work
When we scope the engagement, we aim it where my leverage is highest.
My leverage is highest when
- The problem is messy and nobody has named it yet
- Product, engineering, design and leadership need to pull in the same direction
- Raw research or data needs to become a narrative people can act on
- The work is good but the story isn't landing: the team, the board or customers can't say why it matters
- Every team is working in their own way and predictability is simply a finger in the air
- People need to build their own skills, not just get an answer
My leverage is lowest when
- I'm there to observe and report, not coach and support
- The work is routine tracking and status reporting
- The answer is already decided and just needs a babysitter
- I can't get access to the people or data that matter
To get the most from our time together
- Give me a mandate to coach and change, not just observe and report
- Bring me in before the decision, not after it's made
- Put me in the room with the people doing the work, not just their leaders
- Set goals and a baseline with me up front, so we agree on what success means
- Protect time for reflection. That's where the learning sticks
What we'll watch for
These are the things that slow an engagement down. We agree to name them when we see them.
How we'll handle trade-offs
Some of these principles pull against each other. Here's how we'll resolve it when they do.
What you'll bring to the table
The best engagements are real partnerships. I bring an outside view and experience with problems like yours. You bring what only you have: the context, the access, and the commitment to keep the work going after I leave.
- A sponsor who owns the outcome and can make decisions
- Access to the people, data and systems that matter
- Honest context, including the history and politics behind the problem
- Time from your team to do the work, not just attend the sessions
- Professionalism: on-time, prepared meetings and written follow-through
If things change
- If priorities or alignment shift: raise it directly
- If expectations feel unrealistic: surface it early
- If your team is stretched thin: tell me before it breaks, so we can adjust the scope together
Closing
When communication is open, expectations are clear and nothing is hidden, something shifts. People stop spending their energy protecting themselves and start spending it on the work. Problems surface while they're still small. Decisions stick because the people who live with them helped make them. The team runs on shared principles, not on whoever argues loudest. It becomes safe to show up, speak up and focus on doing great work. That's when people love the work they do.
Getting there isn't easy. It's not a straight line, and there will be setbacks along the way. It takes commitment from leaders and teams alike, and it takes time. I've seen what's on the other side, and it's worth it.
This is a living agreement. If something here is wrong, tell me. If something here works, use it.
We are better together.
Copy it, paste it, ask it anything
Copy the agreement, paste it into your AI, then add a few lines about your team and one of these questions.
Create your own
This prompt turns your AI into an editor. It drafts your manual in your own voice, then asks you where it got you wrong.

