Continuous Improvement
Demonstrate your company’s alignment with the values of public education by committing to the ongoing improvement of your products, services, and organisational learning.
Why: Education is a living process — ever-changing in its needs, practices, and environments. For EdTech to meaningfully serve public education, it must reflect the same spirit of learning, openness, and adaptability. A commitment to continuous improvement means not only refining technical features, but also improving accessibility, pedagogy, and inclusivity over time.
In a European context — where cooperation, reflection, and accountability are valued —continuous improvement is not a one-off project. It is a long-term investment in relationships, user engagement, and shared outcomes. It requires thoughtful use of resources, an open dialogue with educational partners, and the willingness to grow responsibly. As teams grow and knowledge deepens, the organisation’s capacity for thoughtful, meaningful innovation should grow accordingly.
Maturity levels – Commitments to Continuous Improvement
Level Zero - Commit to Starting the Journey: You commit to acknowledging that your product and organisation are not yet fully formed, and you take responsibility for learning and improving with time. At this stage, you ensure that legal and operational basics are in place, and you begin listening to early user feedback, even if you cannot yet respond to all requests. You reflect honestly on the current state of your product and recognise that sustained improvement will require structured effort, resources, and dialogue.
Junior Level - Commit to Listening and Learning: You commit to establishing basic structures that allow you to listen to users and act on what you learn. You begin collecting structured feedback through surveys, interviews, or early testing. You develop an internal improvement process and prioritise updates based on user needs. Your roadmap is shaped by actual usage and challenges encountered in practice. As your team grows, you assign responsibilities for user support, product iteration, and documentation. You invest time in learning from the field.
Medior Level - Commit to Co-Development with Users: You commit to working alongside your educational partners to co-create meaningful, lasting improvements. You embed regular feedback loops into your product cycle — such as quarterly feedback sessions, advisory groups, or collaborative pilots. Product updates follow a transparent schedule, and you communicate the rationale behind changes. Your team includes people dedicated to user engagement, product design, and impact evaluation. You engage in sector conversations to stay informed and benchmark your efforts against the needs of public education systems.
Senior level - Commit to Continuous Improvement as a Core Organisational Value: You commit to making continuous improvement an integral part of your culture, strategy, and contribution to the wider education ecosystem. Your company structure supports long-term learning: every team understands how their work contributes to improvement, and time is allocated for research, development, and reflection. You actively involve educational institutions in long-term innovation partnerships. Your updates are transparent, purposeful, and aligned with pedagogical and public values. You publish findings, share lessons learned, and contribute to the development of standards and practices that benefit the wider field.
Good examples
A company that runs structured feedback workshops with partner institutions every quarter and adapts its product roadmap based on co-developed priorities.
A platform that explains clearly, in multilingual updates, what has changed, why it matters, and how user feedback informed the decision.
An organisation that invests in a dedicated user research and improvement team, and builds long-term relationships with educators across countries.
Bad examples
Data interoperability is not supported
Continually changing UX/UI without a clear guideline or purpose.
A company that promises innovation but delivers only bug fixes, with no input from actual users.
A product that relies solely on founder intuition for development, without engagement from schools or learners