Read the real data first
Why every Yogency project starts with your chats, spreadsheets, and SOPs, not with a screen design.
Most of the systems in my portfolio started the same way: a WhatsApp group, a spreadsheet, and a team that was tired of copying data from one to the other.
The temptation is to open a design tool and start drawing screens. I don’t. Before the first screen, I read the real material: chat exports, the spreadsheets people actually use, and the SOP documents that describe how work is supposed to happen.
Why the data comes first
- The problem is usually already written down. In a customer-service chat log you can see exactly where leads go cold. In a billing spreadsheet you can see which columns are typed by hand every month.
- SOPs become screens. For the Tirtamarta water-utility prototype, every screen was derived directly from the SOP documents, including payroll and payment vouchers. Nothing was invented.
- Numbers keep the project honest. If the system can’t be measured in leads closed, hours saved, or taxes collected, it isn’t finished.
Then ship small
Once the data is understood, the first version goes to the team as quickly as possible. Feedback from the field goes into the next release, and the one after that.
If your process still lives in WhatsApp and spreadsheets, that’s a good place to start. Get in touch.