Product Architecture
Experience Is the Expression of Philosophy
A product is more than a collection of features.
It is the experience of a philosophy.
Every principle described throughout this book must eventually become something learners can see, touch and experience.
If our philosophy says learning should be personal, the product should feel personal.
If our philosophy says intelligence should be invisible, the product should feel effortless.
If our philosophy says relationships matter, the product should strengthen relationships.
The purpose of Product Architecture is to ensure that every experience faithfully expresses the ideas upon which Maigie is built.
Designing From Purpose
Products often begin with features.
We begin with purpose.
Before asking:
“Where should this button go?”
We ask:
“Why should this experience exist?”
Every screen should help someone learn.
Every interaction should remove friction.
Every feature should strengthen progress, relationships or understanding.
Purpose always comes before interface.
The Product Should Feel Smaller Than It Is
Maigie is a rich learning ecosystem.
Personal Learning. Learning Spaces. Classrooms. Courses. Communities. Institutions. Intelligence.
Learners should never feel this complexity.
The product should reveal only what is meaningful in the current moment.
Complexity belongs to the architecture.
Simplicity belongs to the experience.
Context Drives Experience
The same learner may experience Maigie in many different contexts.
Studying alone. Joining a Classroom. Teaching others. Leading a Learning Space. Supporting another learner.
The product should understand these contexts naturally.
Rather than forcing people to switch between different products, Maigie should adapt while preserving a consistent experience.
Context should change the experience.
Identity should remain constant.
Every Environment Has a Home
Every major environment within Maigie should begin with a Home.
Not a dashboard.
A Home.
A Home answers one simple question:
“What matters most right now?”
Personal Learning presents the learner’s next opportunity for growth.
Learning Spaces present the community’s current activity.
Classrooms present today’s shared learning objective.
Each Home is different because each environment has a different responsibility.
The learner should always know where they are and what comes next.
Navigation Should Follow Thought
Navigation should reflect how people think, not how software is organised.
Learners think:
“I want to continue studying.”
“I want to join my class.”
“I want to ask Maigie.”
“I want to review.”
Not:
“I need to open Module 4.”
Navigation should begin with intentions rather than system structure.
The shortest path between intention and action is usually the best experience.
Intelligence Reduces Decisions
One of the responsibilities of Product Architecture is reducing unnecessary decision-making.
Learners should not wonder:
What should I study next?
Where did I leave off?
Which Classroom needs my attention?
Which concept should I revise?
Whenever appropriate, Intelligence should answer these questions before learners ask them.
The product should think so the learner can focus on learning.
Progressive Complexity
The first experience should feel simple.
The hundredth experience should feel powerful.
Beginners should never feel overwhelmed.
Experts should never feel limited.
The product should reveal greater capability as learners, educators and institutions grow.
Complexity should be earned.
Never imposed.
Consistency Builds Confidence
Every part of Maigie should feel like the same product.
Language. Interactions. Visual hierarchy. Behaviour. Intelligence.
Whether someone is studying alone or leading an institution, the experience should remain familiar.
Consistency reduces cognitive effort.
Learners should spend their energy learning, not relearning the product.
Success
A successful product is not one with the most features.
It is one where people rarely stop to think about the interface.
They think about learning.
They think about ideas.
They think about their goals.
The product quietly supports them in the background.
When the experience feels natural enough that technology disappears, Product Architecture has fulfilled its purpose.
Because the best products do not ask people to adapt to software.
They adapt software to people.