S/002AFI Software Labs/2026
Approach
A week with AFI.
- Mon
Kickoff call
Agree this week's priorities with the people doing the work.
Direct access - Tue
Figma link shared
Comment on the flows while they are still easy to change.
Visible decisions - Wed
Written update
What changed, why it changed, and what comes next.
Visible decisions - Thu
Code review
Your team sees every pull request, not just the result.
Shared ownership - Fri
Demo + release notes
Working software on staging, with notes your team keeps.
Shared ownership
Four stages. Something real from each.
001
Discover
Name the problem. We learn the users, constraints, and outcome behind the brief before the team commits to a solution.
Product brief and priorities
002
Shape
Choose the first release. We map the experience, test the important path, and make scope and technical trade-offs visible.
Prototype and delivery plan
003
Build
Release in working pieces. Design and engineering work in short cycles, with feedback and quality checks inside the work.
Usable product increments
004
Evolve
Use the product to choose next. After launch, we review what users do, what the team learns, and where the next improvement earns its place.
Release insight and next steps
