First 30 Days Diagnostic
When To Use
Day 30 is near and you have a notebook of impressions instead of an assessment. You have sat in meetings, read decks and formed a view, and nothing on paper would let the CEO check it. Use this on day one to give the diagnostic an end date, or in week three to turn what you have into a page that stands up.
When Not To Use
If the readout is done and you need objectives with baselines and dates, run 90-Day Plan. If you are still scoping before signing, run Engagement Discovery Questions.
Inputs
- The outcome from the statement of work or charter, and the day-30 date
- What you have gathered for this client: interview notes, documents, figures, each with its source and date
- The people you can still interview, by role
If you have none of this, I start from the outcome and build the questions, the guide and an empty log, and mark the output as a first draft.
Approach
A rapid diagnostic with a written assessment by day 30, following a public playbook for fractional executives and an agency's article on the first 90 days: fix a small number of questions, pull the data each one needs, hold structured interviews that include at least one sceptic, and hand over findings with a ranked list of initiatives, not observations. The failure this prevents is discovery with no end date, and its twin, a finding nobody can trace to a source.
Workflow
- Ask at most three questions: what is the day-30 date; what did the CEO hire you to find out; what have you already seen that surprised you?
- Fix two or three diagnostic questions tied to the outcome, and write a scope guard: what this diagnostic will not look at. Everything else is collected against these questions.
- Build the interview guide: the same core questions for everyone (their goals, where the work breaks, what they would fix first, what they need from your function), plus two per role. Include at least one person likely to disagree with the CEO's view. The playbook suggests five to eight interviews; you set the number.
- Fill the evidence log from what you paste: source, date, what it shows, which question it serves. I add no row you did not give me. Where the story people tell and the numbers differ, log both.
- Write each finding with its mark: observed (you saw it in data or in the room), reported (someone told you), inferred (your reading). Each cites its log rows. A finding with no row is cut or moved to "to verify".
- Rank initiatives, never people, on criteria you set (effect on the outcome, effort, what it depends on), and name one or two early wins that are safe to start now.
- Lay out the readout: to the CEO alone first, then the team. Interviewees are not quoted by name unless they agreed.
Output Format
# First 30 Days Diagnostic
Client: [name] · Outcome: [one line] · Day 30: [date] · Not in scope: [scope guard]
## Diagnostic questions
1. [question the diagnostic must answer]
## Evidence log
| # | Source (person by role, or document) | Date | What it shows | Serves question |
|---|---|---|---|---|
| E1 | [source] | [date] | [as given] | [1 / 2 / 3] |
## Findings
| Finding | Observed / reported / inferred | Evidence rows | Still to verify |
|---|---|---|---|
| [finding] | [mark] | [E1, E4] | [what, with whom] |
## Ranked initiatives and early wins
| Rank | Initiative | Effect on the outcome | Effort | Depends on |
|---|---|---|---|---|
| [1] | [initiative] | [your rating] | [your rating] | [person, data, decision] |
Early wins: [one or two, with owner and date] · Readout: [date with the CEO], then [date with the team]
## Decision
[CEO] accepts, corrects or challenges the findings at the readout on [date], and agrees which initiatives go into the 90-day plan.
Done When
- There are no more than three diagnostic questions and a written scope guard
- Every finding carries a mark and at least one evidence row
- Initiatives are ranked on criteria you set, with your ratings
- The readout has a date, and day 30 has not moved
Quality Bar
- Observed, reported and inferred are never blended into one confident sentence
- No assessment of any individual's performance or potential; findings describe work, process and structure
- Interview notes stay with you; quotes are used by role, and by name only with consent
- No benchmark, industry figure or "typical" number is added to make a finding look firmer
- No finding, number or quote appears that is not in the log you gave me, and nothing seen at another client is used as evidence here
Next
Run frac-90-day-plan (90-Day Plan) to turn the agreed initiatives into objectives with baselines and dated targets.
About the makers
This pack is made by 90n (90n.ai): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
1---2name: frac-first-30-days-diagnostic3description: Structures the first 30 days of a fractional engagement into the two or three questions the diagnostic must answer, an interview guide, an evidence log, a written assessment with findings marked observed, reported or inferred, a ranked list of initiatives, one or two early wins and the day-30 readout. Use for "run frac-first-30-days-diagnostic", "first 30 days as a fractional executive", "day 30 assessment", "diagnostic for a new client", "first 90 days", "turn my interview notes into an assessment", "what should my first month produce", part of the Claude for Fractional Leaders Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/frac-first-30-days-diagnostic6---78# First 30 Days Diagnostic910## When To Use11Day 30 is near and you have a notebook of impressions instead of an assessment. You have sat in meetings, read decks and formed a view, and nothing on paper would let the CEO check it. Use this on day one to give the diagnostic an end date, or in week three to turn what you have into a page that stands up.1213## When Not To Use14If the readout is done and you need objectives with baselines and dates, run 90-Day Plan. If you are still scoping before signing, run Engagement Discovery Questions.1516## Inputs17- The outcome from the statement of work or charter, and the day-30 date18- What you have gathered for this client: interview notes, documents, figures, each with its source and date19- The people you can still interview, by role20If you have none of this, I start from the outcome and build the questions, the guide and an empty log, and mark the output as a first draft.2122## Approach23A rapid diagnostic with a written assessment by day 30, following a public playbook for fractional executives and an agency's article on the first 90 days: fix a small number of questions, pull the data each one needs, hold structured interviews that include at least one sceptic, and hand over findings with a ranked list of initiatives, not observations. The failure this prevents is discovery with no end date, and its twin, a finding nobody can trace to a source.2425## Workflow261. Ask at most three questions: what is the day-30 date; what did the CEO hire you to find out; what have you already seen that surprised you?272. Fix two or three diagnostic questions tied to the outcome, and write a scope guard: what this diagnostic will not look at. Everything else is collected against these questions.283. Build the interview guide: the same core questions for everyone (their goals, where the work breaks, what they would fix first, what they need from your function), plus two per role. Include at least one person likely to disagree with the CEO's view. The playbook suggests five to eight interviews; you set the number.294. Fill the evidence log from what you paste: source, date, what it shows, which question it serves. I add no row you did not give me. Where the story people tell and the numbers differ, log both.305. Write each finding with its mark: observed (you saw it in data or in the room), reported (someone told you), inferred (your reading). Each cites its log rows. A finding with no row is cut or moved to "to verify".316. Rank initiatives, never people, on criteria you set (effect on the outcome, effort, what it depends on), and name one or two early wins that are safe to start now.327. Lay out the readout: to the CEO alone first, then the team. Interviewees are not quoted by name unless they agreed.3334## Output Format35```markdown36# First 30 Days Diagnostic37Client: [name] · Outcome: [one line] · Day 30: [date] · Not in scope: [scope guard]38## Diagnostic questions391. [question the diagnostic must answer]40## Evidence log41| # | Source (person by role, or document) | Date | What it shows | Serves question |42|---|---|---|---|---|43| E1 | [source] | [date] | [as given] | [1 / 2 / 3] |44## Findings45| Finding | Observed / reported / inferred | Evidence rows | Still to verify |46|---|---|---|---|47| [finding] | [mark] | [E1, E4] | [what, with whom] |48## Ranked initiatives and early wins49| Rank | Initiative | Effect on the outcome | Effort | Depends on |50|---|---|---|---|---|51| [1] | [initiative] | [your rating] | [your rating] | [person, data, decision] |52Early wins: [one or two, with owner and date] · Readout: [date with the CEO], then [date with the team]53## Decision54[CEO] accepts, corrects or challenges the findings at the readout on [date], and agrees which initiatives go into the 90-day plan.55```5657## Done When58- There are no more than three diagnostic questions and a written scope guard59- Every finding carries a mark and at least one evidence row60- Initiatives are ranked on criteria you set, with your ratings61- The readout has a date, and day 30 has not moved6263## Quality Bar64- Observed, reported and inferred are never blended into one confident sentence65- No assessment of any individual's performance or potential; findings describe work, process and structure66- Interview notes stay with you; quotes are used by role, and by name only with consent67- No benchmark, industry figure or "typical" number is added to make a finding look firmer68- No finding, number or quote appears that is not in the log you gave me, and nothing seen at another client is used as evidence here6970## Next71Run frac-90-day-plan (90-Day Plan) to turn the agreed initiatives into objectives with baselines and dated targets.7273## About the makers7475This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).