Some of the hardest decisions aren't hard because they're complicated. They're hard because too many things matter at the same time, and it's difficult to keep them connected long enough to make sense of them.
That became obvious once we moved beyond talking and started trying to build Reflection Journal for real.
We weren't short of insight, and we weren't making careless decisions. If anything, we were thinking carefully and trying to be deliberate. But again and again, we found ourselves responding to what was most recent rather than what was most important, even while actively trying not to.
The last conversation carried more weight than it should. The most recent piece of feedback felt disproportionately urgent. Whatever was loudest that day quietly shaped the next decision.
Each of those inputs mattered, and none of them were wrong. The problem was what happened when they were taken one at a time. They pulled us forward in short, reactive steps rather than in a coherent direction.
What we were actually trying to do was hold combinations and patterns in view. We wanted to understand how one decision constrained the next, how technical choices influenced behaviour, and how early signals tended to repeat themselves over time. That turned out to be much harder than expected.
Every individual decision made sense on its own. Each felt justified given what was immediately visible. Over time, context slipped more easily than we realised. Priorities blurred. Things that had felt important a week earlier quietly lost their place, not because they stopped mattering, but because they stopped being visible when the next decision arrived.
This was uncomfortable to confront because it sat at the heart of what Reflection Journal was supposed to do. The whole point was to help people hold onto what mattered over time, not just capture what felt present in the moment. And yet, we were struggling with that ourselves while building it.
That tension made the work slower and more demanding than we expected. Not because the technology was complex, but because getting this right required discipline around continuity, restraint around what we included, and a constant fight against recency. Small design choices had outsized consequences.
Building Reflection Journal forced us to sit inside that reality rather than talk about it from a distance. It made the cost of fragmentation visible and showed us that clarity doesn't come from simplifying decisions, but from being able to keep multiple, competing factors connected long enough to inform each other.
We didn't have a good way of doing that at first. Staying with the problem was harder than moving on.
That difficulty turned out to be the work. Staying with it changed what we noticed, what we prioritised, and the quality of the decisions that followed. Which raises a simple but uncomfortable question about what becomes possible when the important things stay visible, knowing the rest can be revisited later.