Math vs algorithm first
A mathematician on our SwishGuru team, working on shot analysis, thought math-first, not algorithm-first. We lost days debating the theory behind each idea, which a startup can't afford.
So before any development I started async one-to-ones with him: first the system architecture and the expected inputs and outputs, then the maths. After a month we no longer needed them. We delivered the architecture, he polished it, then did the maths. By month three every algorithm change came through without long meetings, because he documented the path from architecture to final proposal himself. The whole team felt it: we ran experiments faster, deployed to testing faster, and sat in fewer meetings.




