Planning is intent; development is words; design is intonation.
Planning is closer to a service, design and development closer to goods.
That's why, when I do design or development, I try to reuse existing (or external) resources as much as possible.
Goods, before the question of "the best," must first deliver consistent quality anytime, anywhere, for anyone. And that quality — like the taste of a Starbucks coffee — must fall within what the user is expecting. Whether it's the finest product in the world is a secondary question.
And if on top of the base feature someone requests small additions or modifications (custom fits) — like trying on a size 260 shoe, finding it doesn't fit, and running to the stockroom to swap it for a 265 — you have to be set up internally to respond as quickly as possible. Peak performance, too, comes after that.
On the other hand, when I do planning I avoid existing templates as much as I can and usually start from a blank page.
Unlike goods, for services the same quality and the same performance every time can actually become a weakness.
No matter how bright the expression and intonation, or how sincere the words, if they're the same when you're sad, happy, or angry — only the content changing — how jarring would that be? —
That's what templates, frames, and frameworks are in planning.
If you start writing a new plan or intent by plugging it into an existing template, then in the end it's not your plan and your intent that get expressed, but — to some extent — someone else's intent and situation back when that template was originally created.
← Back to feed
Slow Days·세번째 아홉
Planning : Design : Development...
This English version was translated by Claude.
