How We Make Decisions

Every product is the result of thousands of decisions. Most of them are small. Some of them are invisible. A few of them shape everything that follows.

What matters isn’t just what decisions are made, but how they’re made — what’s prioritised, what’s resisted, and what’s deliberately left undone.

In tutoring, decision-making happens constantly. Tutors adjust pace, tone, and approach in real time. They choose when to push and when to pause. They make judgement calls based on incomplete information, guided by experience and care. That kind of work develops a particular sensitivity to trade-offs — an understanding that every choice has consequences.

We try to bring that same mindset into how we build.

It’s tempting, especially in software, to optimise for speed. To ship quickly, add features, react loudly to feedback, and move on. Sometimes speed is genuinely useful. Often, it’s just reassuring. It feels like progress, even when it introduces complexity that will need to be untangled later.

We try to slow decisions down just enough to understand their shape.

That means asking simple but uncomfortable questions. Does this make things clearer, or just different? Does it reduce effort for tutors, or shift it somewhere less visible? Does it introduce another decision where none was needed before? If this becomes part of someone’s daily routine, how will it feel after six months, not six minutes?

Many decisions aren’t about what to build, but what not to. Not every edge case needs a feature. Not every request needs to become a setting. Restraint is often the harder choice, especially when it means saying no to something interesting or impressive. But restraint is also how systems stay usable over time.

We think good decisions create fewer future decisions. They simplify rather than expand. They make the right path obvious and the wrong paths harder to wander into accidentally. When that happens, tutors don’t have to think about the system — and that’s usually a sign it’s doing its job.

Decision-making also involves accountability. When something goes wrong, it matters whether there’s a clear reason behind how things were designed. Complexity without intent is fragile. Simplicity with purpose is resilient.

We don’t believe in perfect decisions. But we do believe in considered ones. Decisions made with an understanding of the work they support, the people who rely on them, and the trust they quietly carry.

Over time, those decisions accumulate into a tone. A feeling. A sense of whether something was built with care or merely assembled. That’s what we pay attention to most.