Product
This week I got humbled again.
During the day I tuned the flow and felt the chain was finally complete. At night I used it for real writing and still got blocked by a few startup steps.
That moment was clear: I'm not standing outside the people I build for. I wear both hats. I'm a builder and a user at the same time.
I Don't Observe from Distance
With the builder hat on, I think about activation flow, edge branches, extensibility. With the user hat on: Is it smooth? Is it fast? Does it interrupt me?
Because both feelings live in the same body, I now avoid saying "users might feel..." and write "I just got stuck here."
The First Minutes Are Fragile
Journaling makes this obvious.
What I want is simple: feel something, write it immediately.
What often happens: find folders, patch the title, tweak formatting, locate where I left off. By then, the heat is gone.
So lately I keep pushing one principle: put expression first, then let organizing, archiving, and historical linking run quietly in the background.
In Builder Mode, the Hard Part Is Sequence
Each step is easy in isolation. Sequencing is hard.
Once order is wrong, the experience fractures.
These are the three loops I keep tuning:
- Where to place step one of activation flow so it's accurate without being intrusive
- How to connect the thought process so it doesn't drop halfway
- How to sequence skills and process stages to reduce misfires and rollback
I Want "Being Understood," Not "Finding Entrances"
Older interaction feels like channel switching: find an entrance first, then search for content.
I want something closer to an Information Feed: understand first, deliver next.
That is not UI decoration. It's intent accuracy.
The Hard Part Starts After Intent
Intent recognition is only the first gate. Then comes abstraction design.
Differences between people are concrete:
- Bilingual users need language refinement but don't want their tone flattened
- Creative users don't want to spend energy on wording; they care about high-fidelity content
- Some people want the system to remember old jokes and expressions so they don't repeat themselves
For me, democratizing convenience is not adding more buttons. It's building an abstraction layer people can assemble in their own way.
After It Worked, I Had to Relearn How to Explain It
I tuned this system for many rounds and finally got it working.
But I also know most people don't need internal complexity.
My job is to explain the value clearly while keeping room for participation.
The metaphor I trust now is still Lego:
not forcing people into a fixed menu, but handing them blocks they can shape.
- People can bring their own ideas into the process
- The tool can stay understandable, convenient, and safe for long-term use
I'm still on this path. Design is never a one-shot answer for me. It grows with real use.