Workflows Directory
Find your team’s next superpower.
- Industry: Finance and investment
- Industry: Hardware and physical technology
- Business situation: New business lines
- Clear all filters
Results
9 workflow templates
Assumption map
For a product owner whose plan rests on beliefs nobody has tested: each belief is written down, set against the evidence you hold, ranked by what it would do to the plan, and given a cheap test to choose from. You decide what to test; no evidence is invented.
- Starts it
- Product owner
- Brings
- export, notes
- Gets
- 6 outputs
Authority comparison table
From the opinions, statutes and regulations counsel selected, and only those, the researching lawyer gets one side-by-side table: each authority's court, date, stated issue, operative words, posture and separate opinions, quoted with pinpoints, and a list of every quotation to check. The lawyer decides what applies.
- Starts it
- Researching lawyer
- Brings
- export, notes, document
- Gets
- 3 outputs
Prepares work for a lawyer. Not legal advice.
Channel partner fit review
When a referral, reseller or alliance partner approaches, the founder or head of partnerships gets one review: evidence the partner brings customers of its own, the type that evidence supports, a ninety-day plan with signs to go on or stop, and the commission range that still beats selling direct. A person decides.
- Starts it
- Founder
- Brings
- export, notes, document, pasted text
- Gets
- 7 outputs
Invention disclosure brief for patent counsel
Before the first call with patent counsel, the founder or engineering lead has one factual brief: the invention in the inventor's words, who contributed what and when, every outside demonstration, sale, talk or publication with its date and audience, and the records still missing. Counsel decides.
- Starts it
- Founder
- Brings
- export, notes, document
- Gets
- 7 outputs
Prepares work for a lawyer. Not legal advice.
Pilot build readiness brief
Before a prototype or pilot build, the build lead gets one brief: part shortages, revision conflicts and open actions set against the team’s own build checklist, with allocated parts kept apart from received ones. People confirm; nothing is released.
- Starts it
- Build lead
- Brings
- export, notes, document
- Gets
- 7 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
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
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