Field guide · Before / After
Before / After
Before-and-after weeks, measured in a person’s day: what an assembly changes once it is in place.
§ IBefore / after
The developer’s Monday.
Same projects, same clients hundreds of miles away. The difference is whether each one can see the whole picture.
Monday, before
- Updates scattered across email, text, and phone calls
- Each client unsure they were seeing everything
- The same questions answered again on every project
- Photographs, invoices, and approvals kept apart
- The day spent relaying status
Monday, after
- One portal per client, shaped to how they work
- The whole project visible: progress, selections, approvals
- Questions answered once, where the client can find them
- Photographs, invoices, and approvals in a single view
- The day returned to the building
§ IIBefore / after
The advocate’s new client.
Same diagnosis, same standard of evidence. The difference is whether the packet starts from nothing.
The client, before
- Every packet started from hundreds of papers, again
- Weeks of research before the first useful answer
- Guidelines and resources re-found for each client
- The standard of evidence riding on one person’s recall
The client, after
- A disease-specific library gathered once and reused
- Evidence drawn together and shaped to this person
- Guidelines and resources searchable in one place
- A thorough, personalized packet in days, not weeks
§ IIIBefore / after
The writer’s morning.
Same book, same desk. The difference is whether the morning starts with the work or with the search for it.
The morning, before
- Years of research and drafts across dozens of tools
- Interviews transcribed and then misplaced
- Maps, timelines, and characters held in one head
- The first hour spent gathering, not writing
The morning, after
- Every artifact in one connected, cross-referenced place
- Interviews and research searchable beside the draft
- Characters, chronology, and locations linked, not recalled
- The first hour spent writing
§ IVBefore / after
The wedding designer’s process.
Same couples, same craft. The difference is whether the judgment has a place to live.
The project, before
- Intake, site notes, and inspiration scattered across tools
- The editorial point of view carried only in the designer’s head
- Design decisions re-explained to each vendor by hand
- Documentation rebuilt from scratch for every couple
- No lasting artifact when the day was over
The project, after
- Intake, site analysis, and direction in one structured place
- An editorial reading written down and kept
- Vendor specs and design direction drawn from one source
- Documentation assembled from what is already known
- A keepsake-quality design book for each client
§ VBefore / after
The analyst’s report.
Same datasets, same expertise. The difference is whether every brief starts from scratch.
The project, before
- The same research and prep repeated every time
- Report structure rebuilt by hand
- Quality checks carried in one analyst’s memory
- Interpretation mixed in with routine production
- Cost and turnaround climbing with each report
The project, after
- Datasets pulled and prepared the same way each time
- A standard report structure and reusable analyses
- Quality checks built into the production line
- Judgment reserved for interpretation and recommendations
- Briefs produced faster, consistent, at lower cost
§ VIBefore / after
The carpenter’s project.
Same trade, same craft. The difference is whether the paperwork competes with time at the bench.
The project, before
- Estimates, photos, and punch lists across texts and paper
- Schedules and material lists rebuilt from memory
- A project’s status pieced together job by job
- Client messages spread across a phone
- Admin time competing directly with bench time
The project, after
- One connected workspace, from inquiry to close-out
- Estimates, schedules, and materials in one place
- Every project trackable at a glance
- Client communication kept with the job
- Hours returned to the shop
An assembly is measured in the day it changes.