Missions

What it is

Missions is a digital platform and a set of frameworks for the design and operation of active, meaningful, and continuous learning experiences, with a high degree of flexibility, that incorporates tools for the effective use of AI and data and enables simple connections with other educational or management platforms. Its flexibility allows it to be used for educational purposes or for selection, evaluation, and talent development in any kind of organization.

Missions is not an LMS. It’s a platform for designing learning experiences, and it connects via LTI to whatever LMS you’re already using so you don’t have to change anything about how you manage your students. We don’t compete with LMSs; we sit alongside them. If you don’t have an LMS or don’t want to use one, Missions also works on its own: it ships with user management that’s more basic than a full LMS but enough for many scenarios.

The platform is methodology-agnostic: you can design a mission with whatever pedagogy fits — traditional course, active learning, challenge-based, whatever makes sense for what you’re teaching. On top of that, at Eutika we’ve built our own design framework that we recommend when someone asks where to start; it’s documented in the wiki, in the design section.

Why it exists

Learning isn’t the same as consuming content. Anyone who’s finished an entire course and then realized, when faced with a real problem, that they couldn’t recall what to do, knows this. A good learning experience puts the learner to think, to fail and to try — content is just the material they work with — and designing that takes tools built for designing, not for managing.

That gap is where Missions lives. It fits especially well in online and asynchronous formats, where the design of the experience has to support the learner when no one’s there in person; but it also works as a companion to synchronous or in-person classes, and as support for the assignments a traditional university course already sends students home with.

My role

I came in as a developer. At some point I noticed the need to align the business view and the development view on a few specific points where they were drifting apart, set up a meeting to close those gaps, and from there I started taking on more and more product decisions until the Product Owner role landed on me.

These days I keep the roadmap, hold the overall vision, and stay involved in development. On projects that use Missions I also come in as a facilitator, working alongside whoever is using it — whether that’s an Eutika team or the client’s own team.

Missions is a product owned by Eutika, where it’s designed and developed.