One of my involvements in a product development taught me a lot.
I recently had time to look back and reflect; I looked at what we’ve done and what were some of the things we could have done differently!
We did a lot, and we could have done a better, and differently.
I’ve put the highlight of my learnings in the table below. I might come back to add more. or expand on some of these topics…
| What happened | Learnings (what I would do next) |
|---|---|
| Lots of conversations on requirements but not certainly or clarity | ◾ Make sure the customers are coming to meetings with alignment/agreement (internally) before talking to you ◾ Get certainly and alignment on the requirements (your team and them) ◾ Sign off on WIP requirements before taking more items |
| Trying to deliver a MVP based on the constantly-changing requirements | ◾ Forget about agile (for a short period of time) ◾ Build a MVP in a waterfall fashion ◾ Give it to them so they can start using without chaning their mind again |
| The problem space and the solution space were mixed up (this is not rapid prototyping) | ◾ Keep the customer and their requirements in the problem space ◾ Move to the solution space with your team i.e. Dev/UX/BA and work out a solution ◾ present it back to the customer |
| Build MVP for many personas/users | ◾ Build for the majority ◾ And build it simple |
| Complex processes | ◾ There are historical ways of doing things ◾ You don’t need to (and probably shouldn’t) follow them in the new system ◾ Sometimes you need to bend the process to fit the product ◾ Do current state VS Future state process flows ◾ Map process flows to system flows |
Photo Source: https://unsplash.com/photos/fMh37kIaUbw
