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 −
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.

The goal

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
Part I

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
Questions we'll ask at the end of the engagement
  1. Can they make this call without me?
  2. Are people thinking about their teams and process as products to always reflect on for improvements?
  3. What changed from my involvement?
Part II

Thinking and making decisions

These are the lenses we'll use to look at problems together. Which one leads depends on the problem.

LensThe question I askWhat it looks like
Friction firstWhat is your biggest friction point?I walk every solution back to the problem it solves
Groundwork before the shiny thingWhat does this depend on?The baseline, the context, the user problem, all validated
Outcomes you can measureWhat changes if this works, and how will we know?Every piece of work ties to an outcome we can measure against a baseline, not just a feature we can ship
Structure before blameWhat about the setup makes this hard?A no-blame culture where systems improve, individuals are fearless when it comes to calling out mistakes
Evidence over opinionWhat did we hear, see or measure?A transcript quote beats a confident argument, is there a baseline to kick off of?
Never no, always not yetWhat would earn this a spot now?Ideas wait their turn. Evidence moves them up

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
Part III

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.

ChannelThe placeWhat we'll use it for
SubstackBoutique in the mallOptional reading: the thinking behind how I work. Not where project conversations happen
LinkedInThe mallStaying connected. Anything about the work moves to email or Slack
EmailHomeThe record: recaps, decisions and agreed next steps, so we can always find what we decided
Slack or TeamsThe office floorDay-to-day work: quick questions, quick answers, and unblocking each other between meetings
1:1sA walk around the blockFull context and hard feedback, no filter. Where we build trust and prep the big conversation, so we walk in ready to back each other up
Alignment meetingsThe kitchen tableDecisions that need more than one voice. We leave on the same page, with owners and next steps
In-person meetingsThe workshopDeep work together: workshops, mapping the system and hands-on problem solving

How we'll give and take feedback

How I give it
  • 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
How I take it
  • 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
Part IV

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

Part V

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
When we discuss projects, here is helpful context to line up
  • 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

If you bring me…I'll ask…
A solutionWhat problem does this solve? What's the outcome it's connected to?
“Let's do both”Which would you keep if you could only keep one?
An opinionWhat did we hear or measure? What is your intuition telling you?
A new idea mid-streamWhat does this displace?
A person who's strugglingWhat have we done thus far to help them learn? Were the expectations of success clear?
Part VI

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
Part VII

What we'll watch for

These are the things that slow an engagement down. We agree to name them when we see them.

What I noticeWhy it matters
A lack of transparencyI can't make good calls with half the picture
Blaming a person for a broken systemProblems move to the shadows when people are afraid to talk about them
Shipping without a hypothesisIf we didn't say what we expected, we can't learn from what happened
Process for its own sakeRitual stands in for outcomes
Opinion winning over available evidenceWe'll have the same debate again next month
“That won't work here”Tools don't fail. Humans do. Process changes require ongoing support.
Agreeing in the room, disagreeing in the hallwayThe real objection never gets solved
Learning that stays in one person's headThe next team hits the same wall
Part VIII

How we'll handle trade-offs

Some of these principles pull against each other. Here's how we'll resolve it when they do.

CollisionWhat it means for you
Move fast vs. groundwork firstQuick calls on anything easy to undo. A baseline and a roadmap for anything that isn't
Evidence vs. intuitionI'll ask what the data says and what your gut says. Both count
No blame vs. accountabilityWe fix the system first. Each person still owns their part
Candor vs. kindnessYou'll hear the hard thing, delivered with care
Doing the work vs. teaching itI'll work alongside your team. The goal is that you stop needing me. I do, you watch. You do, I watch. You do, I walk away.
Never no vs. pick oneIdeas don't die, but we work on one thing at a time
Part IX

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
Part X

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.

End of agreement
Ask your AI

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.

Click in the box, select all (Ctrl+A, or Cmd+A on a Mac), then copy.Or download the .md file ↓
Works with Claude, ChatGPT, Gemini or any assistant that accepts long text.
01 Here's what my team is facing right now: [describe it]. What would Rosemary's first 30 days look like with us?
02 What should we have ready before she starts?
03 Who should she meet in the first week, and what should they prepare?
04 What baseline could we set now, and what outcome could we realistically measure by day 30?
05 Where might this way of working clash with how our team works today?
06 What should we expect to have by day 30, and what shouldn't we expect yet?

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.

A
Have writing already?Paste in posts, blogs, reviews, feedback, team docs, old messages. It pulls out your patterns, then asks only what's missing.
B
Starting from scratch?It interviews you, one question at a time, across twenty prompts, then drafts and reviews with you.
Click in the box, select all (Ctrl+A, or Cmd+A on a Mac), then copy.Download the prompt
create-your-own-user-manual.md Select all, then copy

If this reads like a fit, let's talk

Bring the friction you're facing. If I'm not the right help, I'll say so.

Rosemary King · King Catalyst The First 30 Days · A living agreement