The user manual of me
How I think, decide and work with teams. Copy it into your AI, tell it about your team, and ask whether I'm the right fit.
Plain text, ready to paste into Claude, ChatGPT or Gemini.How to use this manual
This is my user manual: how I think, decide, communicate and work alongside a team. If you're considering bringing me into your organization, use it to get a feel for how I operate before we ever talk. The fastest way is to copy the whole thing into your AI tool of choice, add some context about your team and the challenge you're facing, and ask it questions. It won't replace a conversation, but it will make our first one sharper.
Questions to ask your AI
- Based on this manual, what kinds of problems is Rosemary best suited to help with?
- Here's what my team is facing right now: [describe it]. Would Rosemary's approach be a good fit? Why or why not?
- How would Rosemary likely approach her first 30 days with a team like ours?
- Where might her way of working clash with how our team operates today?
- What would we need in place for an engagement to succeed: access, mandate, data?
- How would Rosemary define success here, and how would we measure it?
- What will Rosemary probably ask us in a first conversation, and how should we prepare?
- What should my team know before working with her?
Ten more parts: success, decisions, communication, how to work with me and more. Read the full manualHide the full manual
A proud generalist
My career was built on the principles of Product Craft. I am a proud generalist that has leaned into solving new and diverse problems with every job or client I engage. My perspective in everything I do is focused on value creation, whether it is created by the product I'm building, the process I'm crafting, or the work and ideas I'm putting out into the world. I think in systems, and break down those systems into opportunities and friction points. We get direction from data, and with that direction, we must act to create more data.
Being a generalist is deliberate. I pick diverse, highly complex problems because they make me sharper as a practitioner. Deep expertise is valuable, but it can also distance an organization from the people it serves. Innovation tends to come from people with strong frameworks for learning, who bring fresh eyes and ask what everyone else stopped asking. I pull together the people who hold the right information, organize it into a plan, and help us validate what's real and what's not. As AI turns solutions into commodities, the process of getting to the right one matters more than ever. That's where I focus: critical thinking and craft.
This document is an overview of how I approach work, collaboration, thinking (critical or otherwise.) It's meant to help you understand if I'm a good fit or extension for your team. If you invite me to work with you and/or your team, you accept the following, and welcome it.
I wrote this to help build a strong partnership with you. Treat it as an invitation, and help me understand how you think and what you value in return.
It defines
- What success looks like
- How I think and make decisions
- How I communicate, and what I ask of you
- How to work with me, and where I add the most value
- What slows us down, and how we give feedback to fix it
- Where my principles pull against each other
This isn't a personality profile. It's a working agreement.
How I define success
Success is 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?
How I think and make decisions
These are the six lenses I reach for most. Which one leads depends on the problem.
How I get to a decision
- Decide with the people who have to live with the call, not for them
- 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 standards
My style: Plain, warm, direct. Blunt when something is actually harmful. Kindness always. Nice, iffy before coffee.
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 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
Channel guide
Each channel is a different kind of place, and I show up differently in each one.
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
Honest truths
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 to work with me
What working with me 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 I add the most value
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
How to get the most from me
- 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
Frustration points
These are the things that slow an engagement down.
Where my principles collide
Client accountability
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.
What you bring to the table
- 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 document. 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 manual, 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.

