Draft product updates from code changes
Turn merged code changes into concise product updates that explain the user-facing features and fixes.
A FIELD GUIDE TO AI AT WORK
Good ideas. Better workflows.
Practical recipes for the work your business does every day.
ESSENTIALS / THREE FOUNDATIONS
People. Projects. P&L.
Build the foundations with three practical skills.
Start with what your team does.
Choose your recurring activities to build a starting set.
Test a business idea before committing to development
Assess demand, alternatives, distribution, and delivery risks before choosing a small validation experiment. Keep evidence of the problem separate from enthusiasm for a particular solution.
Keep fundraising materials consistent
Create a deck, memo, or financial model from one agreed set of company facts. Reconcile contradictory numbers before drafting and separate forecasts from observed results.
Draft investor outreach with a specific reason to connect
Prepare a short introduction around an investor’s stated interests and a verifiable company proof point. Produce drafts for review, including a forwardable introduction or a follow-up when relevant.
Build an evidence trail for a service alert
Bring together an alert’s configuration, metrics, logs, and available deployment context so an on-call engineer can assess likely causes without changing the running service.
Turn monitoring events into an on-call handover
Compile a complete alert history for a defined shift and distinguish repeated triggers from currently active problems. Add the outgoing engineer’s notes for the next person.
Check a web release through real customer journeys
Exercise the application in a browser to catch broken navigation, forms, missing assets, and layout problems before customers encounter them. Cover desktop and mobile behavior.
Find which page resources slow the customer experience
Use a measured page trace and network evidence to locate slow loading, delayed rendering, and layout shifts. Turn confirmed causes into a prioritized improvement list.
Add an approval checkpoint to a long-running operation
Design a multi-step assistant workflow that keeps its progress while waiting for an authorized person. Resume only after an explicit decision and handle rejection or timeout as separate outcomes.
Turn an agreed product discussion into a feature brief
Consolidate settled product decisions into a document engineering can review. Make intended behavior, exclusions, and validation decisions explicit before implementation begins.
Break a feature into independently verifiable tickets
Convert a complete feature brief into small delivery units that each demonstrate useful behavior. Keep actual dependencies visible so teams can review the order of work.
Compare interface options before building the product
Use small disposable prototypes to answer a specific interaction or layout question. Compare alternatives with stakeholders and preserve the decisions that should guide production work.
Turn an unclear request into an actionable issue
Investigate a reported problem or enhancement before placing it in the implementation queue. Check existing behavior and prior decisions, then identify the evidence or decisions still missing.
Build a shared product vocabulary
Identify business terms that teams use differently and agree precise meanings. Keep short definitions separate from records of consequential design decisions.
Test an interactive simulation as a lead funnel
Replace a static quiz with a short, mobile-friendly simulation that lets prospects experience a relevant professional task before leaving their contact details.
Offer a personalized professional-profile audit
Turn a team’s profile-review expertise into a self-service diagnostic that provides useful recommendations and introduces a relevant event or service.
Reuse a consistent method for sales-audience research
Package a repeatable research method so an assistant can analyze sales conversations and related lead metrics with the same business definitions each time.
No workflows here yet.
Try a broader search or save a workflow from the library.
The library could not load.
Please check your connection and try again.
171–187 of 371 workflows