Tip for design teams - design for change, not completeness

Real talk for dev teams, design teams who are working on new products!

I want to super encourage you from pain of experience to design for CHANGE not design for COMPLETENESS.

Your product owner is going to want to design for completeness. It is going to drive them crazy that they can’t complete the whole thing.

But almost always if you’re still looking for product market fit, they don’t know enough about the user and the user journey to know how to design for completeness so don’t fall into that trap.

Even if the user could tell you everything they wanted to do, they can’t consume it all at once anyway so you’re not losing anything by not designing for completeness.

But you could lose a lot by not designing for change.

If you’re building a new program and need a digital fix, I can help. Get in touch.

Previous
Previous

You only need 2 things if you are building your airplane while flying it

Next
Next

What’s the difference between a product and a program?