Workflows Directory
Workflow templates for leadership or product management
Results
44 workflow templates, showing 25 to 44
Journey accessibility findings
When a user journey is ready for accessibility review, the reviewer gets a finding list: each finding with its task impact and evidence, the manual checks still required and the limits of the review. The reviewer verifies every finding and agrees fixes with the design owner.
- Starts it
- Accessibility reviewer
- Brings
- export, notes
- Gets
- 5 outputs
Leadership meeting rhythm
Your chief executive gets a proposed calendar of leadership forums and written reports, built from today's meetings and the decisions left waiting: each forum with its purpose, inputs, attendees, frequency and one decision owner, and the hours it gives back. The chief executive chooses; no calendar is changed.
- Starts it
- Chief executive
- Brings
- export, notes
- Gets
- 7 outputs
Manager feedback preparation
Every manager walks into a feedback conversation prepared like your best one: specific dated observations, the questions worth asking, a clear ask and the support on offer.
- Starts it
- Team manager
- Brings
- notes, document
- Gets
- 7 outputs
Ninety-day marketing plan
An owner or first marketing hire gets the next ninety days of marketing on one plan: the stage the business is really in, the moves that fit it, who owns each one, the money and hours they use, and what is deliberately left undone. Every count comes from your own records, and no budget is invented.
- Starts it
- Owner
- Brings
- export, notes, pasted text
- Gets
- 1 output
Premortem before a decision
Before your team commits to a plan that is hard to undo, such as a move, a launch or a new system, a short workshop pictures it a few months on, already failed. The record ranks the reasons, turns each top risk into a check, a warning sign and an owner, and leaves the go decision with the owner.
- Starts it
- Owner
- Brings
- notes
- Gets
- 4 outputs
Presentation outline and talk track
Anyone presenting to a board, a client or a conference gets a storyboard built on one message, then a spoken script for every slide, timed to the slot and true to their own speaker notes. Every fact comes from what the presenter supplied, and the presenter approves the message and the words.
- Starts it
- Presenter
- Brings
- notes, pasted text
- Gets
- 4 outputs
Product pricing options
A product owner weighing how to price or package a product gets one options brief: what each customer group uses, the willingness-to-pay evidence held with stated kept apart from observed, what each option would bill every account, the uncertainties and the tests. It recommends no price.
- Starts it
- Product owner
- Brings
- export, notes
- Gets
- 6 outputs
Product sample feedback revision list
After each round of samples, your product lead gets one revision list by sample version and feature: the changes people agree on, the feedback that conflicts, and drafted notes for the next supplier brief. The product owner decides.
- Starts it
- Product lead
- Brings
- export, notes, document
- Gets
- 7 outputs
Quality management review pack
Before the periodic quality review, the quality lead gets one brief for senior leaders: where each measure stands, complaints and defects, audit findings, action status, and the decisions still open. The leaders decide; the brief claims no compliance with any standard.
- Starts it
- Quality lead
- Brings
- export, notes
- Gets
- 8 outputs
Release notes draft
The product owner gets draft release notes for one shipped release, in words users recognize: what is new, changed, removed and fixed, the steps users must take, and the known limitations. Only what was supplied is described. The owner checks and publishes.
- Starts it
- Product owner
- Brings
- export, notes
- Gets
- 8 outputs
Research summary brief
An executive handed a pile of reports, articles or papers gets one brief: what each source found, where the sources agree and disagree, the limits of each, and exact quotations cited to the page. Built only from the documents supplied. What it means for the business stays the reader's call.
- Starts it
- Analyst
- Brings
- notes, document
- Gets
- 7 outputs
Roadmap tradeoff review
When a new priority arrives, the product owner sees what the roadmap would have to give up to hold it: the capacity gap by team, the work that could move, the commitments and dependencies that move with it, and the questions still open. The owner decides.
- Starts it
- Product owner
- Brings
- export, notes
- Gets
- 8 outputs
Smallest useful release scope
A product owner or founder with more features than capacity gets one page: what is in the first release and what is deferred, all tied to one user outcome, with the reason for each cut. The owner decides the scope; no effort is estimated beyond what is supplied.
- Starts it
- Product owner
- Brings
- export, notes
- Gets
- 7 outputs
Technical demo plan
Before a technical discovery or demo meeting, the account executive and solutions engineer get an attendee brief, a demo sequence built around the buyer's stated workflow from approved scenarios, and open questions. Requests nobody has verified stay questions.
- Starts it
- Account executive
- Brings
- export, notes, pasted text
- Gets
- 7 outputs
Thirteen-week cash flow forecast
The owner sees cash week by week for the next thirteen weeks: what comes in, what goes out, the lowest point and every week below the floor they set, with each assumption written on the page. The forecast informs the decision; the owner makes it, and nothing is paid or moved.
- Starts it
- Bookkeeper
- Brings
- export, notes
- Gets
- 7 outputs
Tracking event plan
Before analytics goes onto a website or app, the founder or product owner gets one plan: the events and properties worth collecting, when each fires, where it goes, what it is called and who owns it, each tied to a question the business needs answered. The owner approves what is collected.
- Starts it
- Founder
- Brings
- export, notes
- Gets
- 5 outputs
Usability test session plan
Before a prototype or a confusing flow goes in front of users, the research lead and product owner hold one plan: who to recruit, the tasks in plain words, the neutral prompts, a blank note sheet and how success is counted. Recording and data handling are listed as decisions.
- Starts it
- Product owner
- Brings
- notes, document
- Gets
- 9 outputs
User research plan
When a design decision needs user evidence, the research lead gets one study plan: what the team needs to know, what evidence already exists, method options with their hours, participant criteria, permissions needed, how answers will be read and what the study cannot establish.
- Starts it
- Research lead
- Brings
- export, notes
- Gets
- 9 outputs
Weekly owner business brief
Each Monday the owner gets about one page built from the exports they supply: cash, last week's sales against the week before, pipeline movement, the week's commitments and a watch list, with one item to look at first. Every figure names its source, and every missing export is named.
- Starts it
- Owner
- Brings
- export, notes
- Gets
- 8 outputs
Workflow fit check: is this piece of work ready for AI?
Before you build anything, run one piece of work through six checks and get a straight answer on one short page: build it, build one part, do something simpler first, not yet, or leave it with your people. The owner decides what gets built first, with the reasons in front of them.
- Starts it
- Owner
- Brings
- notes, pasted text
- Gets
- 6 outputs