problem 01/02
Everyone used one WhatsApp group or paper notes, so there was no clear record of anything.
--the-fix
A Slack channel per project
Each project has its own channel, with its updates set out clearly in one place.
~/recent-builds/project-channels
One channel for every project
Team communication moved off one WhatsApp group and paper notes into Slack, split by project, so updates are clear and easy to find.
- client
- Client under NDA
- type
- Workflow
- status
- live
- tools
- slack
~/what-broke → what-we-built
problem 02/02
Information lived in people's heads and got lost between them.
--the-fix
Decisions and files kept together
Decisions, files and updates stay with the project they belong to, where anyone on the team can find them.
~/how-it-runs
What it does, step by step.
Each circle is one step, in the app where it happens. Click a step to see what it did.
ran 4 steps
- SlackAn update is posted in the job's own channel#baker-st-reno · Dan: tile change approved
- SlackThe file stays with the decisiontile-spec.pdf attached in the thread
- SlackOnly the people on that job are notified3 people pinged, not the whole team
- Only if: urgent.SlackUrgent things go to their own channel#ops-urgent · supplier PO needed today
example data
$ next --step
Want something like this?
Tell us about it on a free 20-minute call. If it can be automated, you'll leave with a clear idea of how and what it would cost. If it can't, we'll say so.
Prefer email? ari@byaryeh.xyz