Not to explain the joke, but: this is a joke. To be fair, I understand that there are diamonds to be doubled, user problems to be user researched, and designs to be processed, thinked, and atomized. But what about just reasoning through the specific use case you’re in, rather than throwing an opinion piece at your problem?
In my view, there is no checklist, “framing,” “methodology,” “process,” “way of thinking,” or any other prescribed ideology or pattern that can replace good, solid sense.
Then how should I work?
Work how you think is reasonable, and how your team wants to work.
What about using {{DESIGN_METHODOLOGY}} I read about?
Do not impose process on yourself — or your peers — due to a sense of peer pressure.
Design Thinking, rethought
With all this being said, I’m proposing a new design process/framework/methodology/thought/etc.: UYBJ. This stands for “Use Your Best Judgement.” Some people like to refer to this as “common sense,” or “doing what you think is right.”
How do I engage in UYBJ Thought?
Here’s how it works:
Step 1. Do things that are consistent with what you personally believe to be true.
Some examples of UYBJ:
- If you believe that you have everything you need to move forward on a task: do not “do research,”
- If you see no advantage in having a design system: don’t make one,
- If you’d like to jump into Figma and start designing: don’t make “lofi prototypes,”
- If you would like to make the product look or behave better: do so.
Final thoughts
If the market sees no value in your product, people won’t patronize your business (e.g., if it’s a game: it’s not fun; if it’s a movie: it’s not interesting; if it’s a tool: it’s not useful; etc.) — no methodology or thought will change that. Here’s what will: offering a product/feature that does generate value for people in some way.
Using a “methodology,” “process,” or “framework” when trying to settle a discussion can seem an unassailable approach. But you know what actually is? Good reasoning.
