Why Nemo?

The limiting factor for software isn’t whether any given thing is possible.

It’s how to actually decide, communicate, and course-correct effectively within the complex web of data, systems, goals, teams, etc that we work in.

Every team at every company has to:

  • Design and decide while balancing competing goals and constraints.

  • Cut costs without breaking the business model.

  • Make and update plans in the context of accelerating tech and market change.

  • Stay aligned across multiple goals across different functions.

Even though these are crucial and common tasks, we haven’t had great tools to help us actually work through them.

  • Problem solving: how do you work through a complex problem to come up with a potential path forward? Meetings? Docs? Someone disappears for a while and returns with a context-free proposal? How long does that usually take? Those meetings are expensive - are they worth it? How often do you miss some important element, and spend as much (or more!) time cleaning up after your project than on the initial implementation?

  • Cost cutting: spreadsheets are deceptive. Without understanding the relationships between teams, systems, processes, and the business, it’s too easy to lose a million dollars trying to save ten grand.

  • Planning: planning’s easy if you have one clear goal, independent teams, and rapid feedback cycles for everything. Unfortunately, we’ve never met anyone who gets to work in that magical world. Instead, coming up with a balanced set of priorities is hard for leaders, and the result often seems arbitrary to the rest of the org.

  • Staying on track: coming up with a plan is one thing. Evolving that plan as dates slip, new goals get set, and you learn new information is the hard part. Any given change has a lot of potential ripple effects - are you hoping to remember every single one in the moment?

How does Nemo help?

  • Quickly get connections out of your head into a visual form. Making a map helps you think through a problem, like writing, but it works better for complex situations than a linear document.

  • Focus on meaning, not formatting. Nemo’s optimized for iterating on connected ideas. Connect ideas in meaningful ways, compare those connections across nodes, label concepts, and more. There isn’t One Right Way to communicate this complicated stuff, so Nemo’s designed for change.

  • Get to a common understanding with your team. Ever had a productive meeting in front of a whiteboard, taken a picture, and never looked at the picture again? You should have a shared model of your product, system, business, architecture that you can build on over time and reuse in different situations.

  • Keep using all the tools you already use. Nemo’s for making connections between what exists (and what could exist!) - not being the single source of truth for every possible question.