Get these posts delivered to your inbox once a week:

October 17, 2020     Daily Post

Conversations VS Deliverables

Conversations VS Deliverables

What do designs, business plans and product development plans have in common?

They’re conversations, not deliverables.

For instance, design software isn’t for making pixel-perfect designs. It’s for allowing creative mediums to converge in one place prior to preparing them for development. Illustrations, animations, things that if you were to take straight into code may not quite work together in quite the same way without first having a canvas to spike it all out in varying levels of fidelity.

Design files aren’t supposed to be perfect: They’re supposed to be enough to inform the creative and the code how to come together.

Business plans aren’t supposed to be perfect: They’re supposed to be enough to inform operations, marketing, product, finance and more how to come together, not correctly predict the future and reward our minds for getting there in advance.

Product development plans aren’t supposed to be perfect: They’re supposed to enable the product and the marketing to be the same thing, by giving a language for product and marketing minds to converge over together, rather than merely producing widgets others have to figure out how to peddle.

Are you creating deliverables where you should be creating conversations? What would change in your body of work if you changed that?