Bring a 90-Day Plan to the Interview. Almost Nobody Does.
One page, written before you are hired, showing what you would do first. It changes the conversation from assessment to collaboration.
This is the highest-return hour of preparation available to a candidate, and it is unusual enough that it is remembered.
What it is
One page. What you would do in your first thirty, sixty and ninety days if they hired you. Written before the interview, sent after it, or shared on screen if the conversation allows.
It works because it moves the discussion from "can this person do the job" to "here is how we would work together". You are behaving like a colleague before you are one.
The structure
Days 1–30 · Learn. Who I would meet, what I would read, what I would ask. Name real things from the job description and from what they told you in the call.
Days 31–60 · Contribute. The first thing I would improve, and why I picked it. Small and finishable, not a reorganisation.
Days 61–90 · Own. What I would be running independently by then, and what "good" would look like.
Keep it to one page. A three-page plan reads as someone who has already decided how their company works.
A worked fragment, for a support role
Days 1–30. Sit with every member of the support team for thirty minutes each. Read the last three months of tickets to find what actually breaks. Learn the product properly by working through the onboarding as a new customer would. Meet whoever owns the help centre.
Days 31–60. You mentioned first-response time is the metric under pressure. My first move would be to categorise a month of tickets and find the five issues that generate the most volume, then write proper templates for those. In my last role that took first response from about eight hours to under two.
Days 61–90. Owning the queue independently, with the help centre updated for the top five issues so a portion of them stop arriving as tickets at all.
The rule that makes it work
Everything in it must come from something they said or something publicly true about them. A generic plan is worse than no plan, because it proves you did not listen.
So take notes during the interview and write it afterwards. That is usually better than arriving with it pre-written, because it can reference the actual conversation.
How to send it
With the thank-you note, the same day.
"Thanks for the conversation — the point about first-response time stayed with me. I put together a one-page view of how I would approach the first ninety days. No obligation to read it; it was useful for me to think it through either way."
That last line matters. It removes the pressure and makes the gesture read as genuine rather than as a tactic.
What it also does for you
Writing it forces you to work out whether you actually want the job. More than a few people discover, halfway through a ninety-day plan, that they have nothing they want to do there. That is worth knowing before an offer, not after.
Interview preparation, recorded and reviewed against the questions you will really face, is Stage 4. See Stage 4.