Play Center began with a simple gap: learners could know the form, but not always the fit — what to use, where, and when.
So I asked, why not design a system around meaning, decisions and play?
Built around how learners think, decide and use language.
Recognize · Relate · Organize · Apply · Repair · Produce
Learners could know the rule and still hesitate when the situation changed. That told me the real challenge was not remembering grammar — it was knowing what fits, where, and when.
A learner might know that must is stronger than should, or that bored and boring are different, yet still struggle when the wording or situation changes.
I realised that recognising a rule and knowing how to use it are two different things.
I changed where I started.
Instead of beginning with a grammar rule and asking how to turn it into an activity, I begin with the situation: What is happening? What does the learner need to work out? What decision would show understanding?
Then I design the experience around that decision.
Once I understood the problem, I needed a repeatable way to design around it. I start with the situation, work out the meaning, define the decision the learner needs to make, choose the right kind of play, and then look at what their response tells me.
What is happening here? I start with a context the learner can recognise and make sense of.
What does the language actually mean in this situation? I look for the distinction underneath the grammar rule.
What does the learner need to work out? I define the choice, correction or response that would show understanding.
What kind of interaction makes that decision useful and engaging? That determines the game.
What does the learner’s response tell me? I use the learner’s response and feedback to see whether they understood and could use the idea.
Each game asks the learner to do something different with language — recognise, relate, organise, apply, repair or produce.
Choose what fits the meaning and situation. The learner makes a quick but meaningful language decision.
Connect ideas that belong together. The learner identifies the relationship between them rather than recalling two separate facts.
Sort language into meaningful groups. Organising the items helps the learner recognise the underlying pattern.
Use an idea in a new situation. The learner carries what they know into a different context rather than repeating the same answer.
Find what is not working and fix it. The learner identifies the problem and restores the intended meaning.
Complete, change or create language directly. The learner works with greater independence and less support.
Once the games started taking shape, I needed a simple way to keep the product coherent as it grew. I organised Play Center around five connected parts: learning goals, content, experience, learning evidence and quality. Together, they give me a structure for adding new topics and games without losing the learning logic behind the product.
What should the learner understand, and what would show me that they understand it?
The topics, examples and activities that give learners something meaningful to work with.
I match each topic to the games that suit it best instead of forcing every topic into every format.
I look at what learners recognise, connect, organise, apply, repair and produce to understand how they are progressing.
I use clear checks so new content stays accurate, useful and consistent as Play Center grows.
Every game gives me evidence of what learners understand and how confidently they can use it. Behind the experience, I use clear checks to keep the content accurate, useful and consistent as Play Center grows.
The six games ask for different levels of independence. Some help the learner recognise or connect an idea; others ask them to apply, repair or produce language more directly.
Before new content goes live, I check that it belongs, works clearly and meets the standard I set for the product.
Once the idea was clear, I had to turn it into something real. That meant moving back and forth between learning, content, interaction, code and testing — making decisions, building them, seeing what worked, and improving what did not.
I started with the moments where learners hesitated, guessed or knew the rule but could not use it confidently.
I turned those moments into clear learning goals: what should the learner understand, decide or be able to do differently?
I worked out how the topics, games, content, progression and feedback needed to fit together.
I turned that structure into playable screens, interactions, content and feedback in the web application.
I kept checking whether the experience was clear, useful and supporting the intended learning — then adjusted the content, rules and interface.
I deployed Play Center as a beta web application so users could test the games, interact with the learning experience and provide feedback before wider release.
Building Play Center meant connecting how learners learn with how the product is structured, experienced, built and improved.
Learning goals, learner decisions and evidence of understanding.
Problem, interaction, feedback and the wider system working together.
Content structured to grow without losing its logic.
Different game mechanics for different kinds of thinking.
Build, test and keep the product reliable as it evolves.
Open Play Center and see the thinking in action.