MANABU2 TEAM
Manabu2 is an LMS for rebuilding a company's talent strategy from the inside. Handing out courses changes nothing on its own, so the workstreams run all the way to the working process itself.
WHO IT IS FOR
The people learning, the people teaching, the people responsible for capability, and the people reading the numbers. They need different things, so the workstreams divide along those lines.
The people actually taking the course, and giving up time for it.
Workstreams serving them10
The people deciding who learns what, and watching how far it got.
Workstreams serving them12
The people turning what the floor knows into material.
Workstreams serving them4
The people judging capability by what the business can now do.
Workstreams serving them5
The people wiring it into HR and line-of-business systems.
Workstreams serving them1
THE ROSTER
One workstream, one objective. What follows is not a snapshot of who is busy today — it is the set of workstreams this product needs.
7
What a learner actually touches, and what carries the learning through to the work.
Learning experience
Make a course finishable, and never be the reason someone stops.
Learners
Course authoring
Let the people who know the work write the material in their own words.
Authors
Tests and assessment
Catch the illusion of understanding, and measure how far someone actually got.
Learners HR
Course packaging and credentials
Bundle courses into a path, and issue what finishing it is worth: a named certification or a certificate of completion.
HR Authors Learners
AI learning assistant
Explain it a different way at the point where someone is stuck, and stay until it lands.
Learners
Skills and people data
Show what people can do in terms of the work, not a list of courses attended.
HR Leads
Connecting to the process
Build the path by which what was learned reaches the procedure people follow.
HR Leads
2
Learning does not only happen at a desk. These keep it going on the move.
iOS development
Let someone keep learning on iPhone and iPad, including between other things.
Learners
Android development
Deliver the same on Android, so the handset is never the reason learning stops.
Learners
2
Taking the learning machinery Manabu2 has built and shipping it into other subjects. The repositories are separate; the team watching them is not.
Spin-off apps
Ship focused apps of their own — such as Wakaroute for junior high entrance exams — shaped for one subject.
Learners
Breaking it into services
Split the learning machinery into parts, so a new subject such as security training can ship quickly.
1
What the screens can do should be reachable from outside tools and AI agents too.
MCP / API
Let outside tools and AI agents work with Manabu2's features and data.
Developers
3
Building it is not enough. These carry someone from never having heard of it to using it.
SEO and content
Be findable, and say what it does before anyone has to ask.
HR Leads
PR / SNS
Keep saying, outside, what this is actually for.
HR Leads
Sales
Find the right prospects, make the case, and keep the thread alive. An agent researches and drafts; a person has the conversation.
HR Leads
2
Nobody gets stuck after they start, and what they tell us turns into a fix.
Help content
Let people solve it themselves instead of waiting for support.
Learners Authors HR
CS / QA
Answer what comes in, and turn it into a fault that cannot happen twice.
Learners HR
1
The workstream that runs before anything is built: what was asked for, read against how it is used.
Feature requests
Gather what users ask for and what usage shows is missing, and decide what gets built next.
Learners HR Authors
3
It stays up, it stays protected, and the billing adds up.
Server watch / log analytics
Find errors and slowness first, so nobody meets them mid-task.
Security
Check on every change that what must be protected still is.
HR
Billing
Bill what was used, correctly and on time.
HR
WHAT SHIPPED
What those workstreams actually turn into: the latest releases from Manabu2.
THE LOOP
Every workstream turns the same way. A person sets the objective, an agent does the work, and the decision to ship comes back to a person.
See the eight stepsA learner, an HR lead or an instructor — who it gets better for, and how. People decide that.
One session per workstream, started with the code conventions, the past decisions and the current numbers already in hand. A workstream that turns into a long piece of work gets a branch of its own.
Changes go out small, through review and an automated test suite, onto a staging environment — and a person makes the call to put them live.
Did they finish it, and did the work change afterwards? A completion rate on its own is not enough.
ONE AT A TIME
The workstreams do not all run at once — one moves at a time. Holding both the course content and the spin-offs works because one conversation only ever holds one workstream.
Work on authoring does not queue behind issuing credentials. Each moves on its own objective.
Code conventions and the quality bar are the same across the whole project. What stays separate is the mission and the context around it.
Decisions accumulate inside each workstream, so picking it up again does not start from zero.
When a workstream turns into a long piece of work, it moves to a branch of its own. The work is kept apart the same way the context is.
Many small changes rather than one large one — each inside a range we can roll back.
STILL OURS
More agents does not move the responsibility. That stays with people.
We can do more than before. That is exactly why the decisions worth our time are the ones to decline.
Dates, estimates, quality. A company promises those, and a company is people.
Review and merge. A person presses the last button.
LET'S TALK
The way we run Manabu2 is the way we run the work clients bring us. Tell us what you need moved first.
Talk to us