How to answer repeated roadmap questions from executives on Mac: a PM routine for 2026

Your week has a familiar shape. A director asks where the search rework landed. A little later, a VP asks the same thing in a different channel. You answer both from memory, and the answers do not quite match. The question is not hard. It keeps coming back because the answer lives in your head and in old threads, not in one place people can find.

What repeated roadmap questions cost you

No survey I found measures how often product managers get repeat roadmap questions. The figures below are general knowledge-worker numbers. They point the same way, but they do not prove your week looks like someone else's.

Start with money, because it is the easiest to picture. The Bureau of Labor Statistics lists a median base pay of $49.19 an hour for project management specialists in May 2025. A product manager is a different job, so treat the figure as a rough stand-in. Base pay also leaves out benefits and overhead, so your real cost is higher.

Turn the cost into a number you can defend

Use one simple formula. Add up the minutes each repeat answer takes, including the time to find the context. Multiply by the repeats in a week. Then multiply by your hourly base pay. Count for one full week before you estimate. A guess made at the start is easy for a skeptical manager to dismiss.

1. Search Slack and your doc tool for roadmap, timeline, launch and status. Cover the last two weeks.
2. Count each message or meeting question where you explained the plan again.
3. Time one typical repeat answer, from reading the question to sending the reply.
4. Multiply the total minutes by your hourly base pay. Save the figure and compare it next month.

Why executives keep asking the same roadmap questions

Executives are usually not ignoring the roadmap. They cannot find the current version quickly. They also do not trust that a copy they saw last month is still true. Atlassian reports that 56% of employees still ping someone or schedule a meeting to get the information they need. Asking is often the fastest path to an answer.

Distance adds to the problem. Berkeley Haas summarized a Microsoft study of over 61,000 employees. Workers collaborated less across groups, and written channels replaced live talk. A written update reaches people unevenly, so each leader sees a different slice of the plan.

Find the questions before you answer them

Most repeat questions follow a pattern. The same few themes come back, such as a date, a scope change or a dependency. Log them for one week, and the pattern shows up. Memory is not a reliable log, so use a sheet.

In Google Sheets, make four columns: date, who asked, the question in their words, and theme. Select the header row and choose Data > Create a filter. Then filter by theme to see which answers you repeat most. To count distinct themes quickly, read how to count unique values in Google Sheets on Mac.

Watch for questions that look repeated but are not. A director who asks about a date after a scope change needs a new answer. Log the change as well as the question, so you can tell the two apart later.

Write one standard answer for each repeat question

Write each answer once, in the same format. Two lines work for most repeats. The first line gives the current status and date. The second line says what changed since the last update, then links to the source. Date every answer, so a reader can see when it was last true.

Store answers where your hands already are. That can be a Notion page, a pinned message in the channel or a snippet in your dictation setup. Lazur dictates clean text at the cursor in any app when you hold fn. It also keeps snippets, a personal dictionary and clipboard slots.

Make one roadmap link the answer

The fastest fix is one link that always shows the current state. Productboard documents the steps for its own boards. Open Share > Publish, then Copy link. Anyone with the link can view the board unless you set a passcode. Only makers or admins can publish, and the board must sit in an open teamspace.

Know what viewers see before you share. Productboard's help page says viewers see item names, descriptions, status values and card attributes. They cannot open other boards or the rest of the workspace. Treat anything on the card as visible to anyone with that link.

Decide what goes in the shared view

• Include the status, the current target date, the owner and the last-changed date.
• Include one line on what is committed and what is only a hypothesis.
• Leave out salary, hiring plans, customer names and unreleased pricing unless your company says they are safe to share.
• Leave out internal debate and half-finished options that will confuse the reader.

Set one update time, then keep it

A fixed time changes behavior. If executives know the roadmap note lands on the same day each week, they stop asking in the meantime. Pick a slot your team can keep, and post the note in the channel executives already read. Put the slot on your calendar, too.

Ask Lazur out loud to set a reminder or a Calendar event for the update. Lazur sets Apple Reminders and Calendar events by voice. Check the item once after you set it, so you know it saved. Keep the reminder short, so you do not skip it in a busy week.

When an executive asks anyway

Some people will still ask. Answer with the link and the one line that changed. Do not reopen the whole plan in the thread. If the question shows the roadmap is unclear, say so and offer a short review call. That costs both calendars less than another long thread.

Ask what decision they need to make. Many repeats come from someone who has a choice coming up and wants the date to lock in. A direct question often ends the loop faster than any document. Write down the answer, then add it to your standard replies.

Mistakes that make repeat questions worse

• Sharing a draft as if it were final. Mark drafts clearly, or keep them out of the shared view.
• Updating the link but not the copies in slides and docs. Old copies restart the cycle.
• Answering only in direct messages, so the next person asks the same question again.
• Putting dates in the roadmap that the team has not agreed to. The roadmap then reads as a promise.
• Writing long updates nobody opens. Two lines and a link usually beat a full page.

Check whether the routine works

Count repeat questions for a month, using the same search terms and the same sheet each week. A drop is a useful signal, but it is not proof. I did not find a controlled study showing that a roadmap page or FAQ cuts repeat questions. Your own count is the best evidence you will get.

Also check quality. A quiet inbox can mean people stopped asking because they stopped trusting the roadmap. Ask two executives each month whether the update answered what they needed. Keep the parts they say help.

Where Lazur helps, and where it does not

Lazur is a voice assistant for the Mac. Hold ⌥ ⌘ to ask about anything on screen, and Lazur answers out loud. Hold fn to dictate text at the cursor in any app. Use it to draft the two-line answer, read back a dense status page, or point at the control you need.

Lazur does not click buttons or operate other apps for you. It does not post to Slack, edit your roadmap or know what an executive means. You read every draft and send it yourself. It also cannot give a roadmap a clear owner. That still takes a person.

Sensitive details in a shared roadmap

Roadmaps often mention customers, pricing, hiring or unreleased features. Before you share a link outside your team, check your company's rules for that kind of detail. Some companies require an admin review. Follow your employer's rules on client or patient data, even when the roadmap feels internal.