A careful pilot.
Built around your learners.
Explore how Nihoner’s courses, references and practice tools could support an existing Japanese programme. Every engagement begins with educational goals, data needs and a realistic technical scope—not a one-size-fits-all promise.
Support the programme you already run.
Nihoner is best considered as a supplementary practice and reference environment. Curriculum ownership, assessment decisions and learner support remain with the institution.
University modules
Offer optional practice around a lecturer-led module, with agreed content links and a limited learner group.
Language programmes
Use references, flashcards and practice activities between teacher-led sessions.
Public-interest projects
Build a ring-fenced, free resource around exchange, participation or Japanese-language access.
Separate what exists from what needs discovery.
This avoids procurement surprises and makes it easier for academic and technical teams to assess fit.
| Area | Status | How it can be considered |
|---|---|---|
| Courses and lesson library | Available | Review the relevant course and lessons with the teaching team before assigning them. |
| Grammar, vocabulary, kanji and dictionary references | Available | Use as supplementary lookup and independent-study material. |
| Exercises, games and flashcards | Available | Select activities that match the programme’s learning objective. |
| Learner accounts and progress views | Available | Demonstrate the current workflow and agree which information the institution actually needs. |
| Institution administration dashboard | Pilot review | Validate roles, roster workflow and reporting with a small test group. |
| LMS, SSO or custom integrations | Needs discovery | Document the target system and required standard; no compatibility is promised before testing. |
| Custom curriculum or assessment | Needs discovery | Requires academic review, ownership terms and a separate scope. |
Small enough to learn. Clear enough to evaluate.
Discovery
Identify the learner group, purpose, teaching context, stakeholders and non-negotiable requirements.
Written plan
Agree scope, duration, responsibilities, support, data handling and success measures.
Limited launch
Start with a manageable group, an orientation and a clear route for questions or withdrawal.
Evidence review
Report usage and feedback honestly, include limitations, and decide together whether to continue.
No invented success stories. No guaranteed outcome.
A pilot should create evidence that both parties can inspect. Until that evidence exists, Nihoner will not publish institutional performance claims.
- 参Participation
Invited learners, activations, voluntary use and completion—reported separately.
- 学Learning evidence
A baseline and post-pilot task chosen with the teaching team, not a marketing proxy.
- 声Learner and educator feedback
Questions agreed in advance, with critical and positive responses represented.
- 限Limitations
Selection bias, incomplete use and other constraints documented alongside results.
Review the facts before any learner is enrolled.
A public policy page is not a substitute for an institutional assessment. Before a pilot, Nihoner will document the proposed data flow and answer the institution’s security, privacy and accessibility questions for the actual scope.
Data minimisation
Agree which account fields are necessary, who can access them and how long pilot records should remain.
Policy review
Review the privacy policy, DPA information and relevant terms before launch.
Accessibility review
Test the proposed learner journey with the institution and document known issues and reasonable adjustments.
Bring one learner group and one clear objective.
Tell us who the pilot is for, what it should support, your intended timeframe and any mandatory technical or data requirements. We will respond with questions before proposing a scope.