13:30 · Before Cowork
The Build Map
You are not becoming a software engineer. You are looking for a software-shaped solution to your own work.
Start with the Pain Card and the Solution Architect's Build Brief. Classify the recommendation before Cowork.
Build software to do your own job better — not software for software's sake.
What changes?
The pattern is your build's relationship to the work: automate it, upgrade it, or invent something new.
What relationship does your build have to the work you do today?
The room result appears once you vote.
Who depends on it?
The right quality bar comes from who uses it and what a failure would cost.
What is the lowest delivery bar that honestly fits?
The room result appears once you vote.
For today, default to Prototype or Personal software. If the honest answer is Production or Product, shrink the scope or plan a proper handoff.
Lifespan
Disposable is a lifespan, not a quality class
A prototype, a personal tool and even production software can serve one goal or one period and then be retired. That is not failure. When building is cheap, temporary tools become rational.
Where should you look?
Scan your own week, not a generic tutorial.
Presentation work
Do you explain, compare, calculate, onboard or report the same thing repeatedly?
Examples
Interactive explainer, calculator, comparison tool, walkthrough, status page, lookup tool.
Content work
Do you repeatedly turn one kind of content into another?
Examples
Transcript-to-brief pipeline, one source to several formats.
Data work
Do you pull, clean, reshape or explain the same numbers?
Examples
Living dashboard, data translator, recurring analysis.
Document work
Do you fill templates or perform the same operation across many files?
Examples
Template filler, bulk rename, convert or check.
Inbox work
Do you repeatedly collect, classify, chase or route submissions?
Examples
Intake, triage, follow-up queue.
Admin work
Do you repeat rules, checks or handoffs that nobody learns from?
Examples
Checklist engine, tracker, reminder or exception flow.
Six starting points
Two per pattern. Thought starters, not homework.
Automate
The Friday export
Drop in the raw spreadsheet, preview the transformation and download the trusted old output.
The invoice pile
Read invoices or receipts, normalize fields, flag low confidence and duplicates, then produce the tracker for review.
Upgrade
The live report
Replace recurring snapshots with one current page that answers the key questions.
The what-if slider
Expose price, volume, timing or headcount assumptions and show how the outcome moves.
Invent
The watcher
Monitor changing sources, filter noise, remember history and alert only when something matters.
The pattern reader
Read the pile nobody has time for, cluster themes, compare segments and link conclusions back to source passages.
Build or borrow
Just because you can build it does not mean you should
If an approved tool or agent solves enough, use it.
A build you have to maintain is a cost. Borrowing is the cheaper first answer.
If the missing value is a connection or last mile, build only that thin layer.
Bridge the gap between what exists and what you need. Nothing more.
If other people depend on it, raise the delivery bar.
Dependence changes the class: owner, access, support and realistic reliability.
If it sends, spends, deletes or decides, require an explicit human checkpoint.
Consequential actions stay under review, however good the helper gets.
The win is not more software. The win is better work.
Handoff
Carry four things into Cowork: the Pain Card, the recommended solution, the build pattern, and the delivery bar.
Take this decision into Cowork →Sources
Adapted for this session from The AI Daily Brief, “How to Start AI Coding If You Haven’t Yet,” 29 Aug 2026.