The Innovation Capability Is Learnable
Students who arrived at PolyU’s Innovative Business Design believing they were “just designers” discovered they could design systems. Students who saw themselves as “just engineers” discovered they could strategise.
That taught me something no other work could have: these capabilities are learnable, and they are learnable through deliberate practice.
I did not learn them in order
Industrial designer first — consumer electronics, home appliances, toys and telecom devices for global markets, and a product that ended up in Iron Man. I thought design was about making things look good. Design is about making things work for people.
Then brand building at P&G, working on billion-dollar products in China. I was an introverted designer, not a natural salesperson. I learned to be an Activator through necessity.
Then a digital transformation across seven Asia-Pacific markets — a portable AI skin analyser, a virtual makeover app, and one hundred thousand device pre-orders in six months. That made me a Strategist and a Technologist whether I wanted to be or not.
Then coaching 45+ startups at HKSTP, and teaching at PolyU. None of it came from natural talent. All of it came from stacking skills one on top of another, mostly by failing forward.
Innovation Capability is learnable — and it is a practice
The four capabilities are not innate talents reserved for a gifted few. They are practices. You do not arrive. You keep showing up.
Which brings the honest part: I am still working on all four. The Strategist still catches me deciding on instinct when I should have built an evidence ladder first. The Wizard still over-designs before listening enough. The Activator still retreats into analysis when the situation calls for a story. The Technologist still designs systems he has not yet scaled.
That is not a confession. That is the practice.
One tool that makes teams sharper
One tool I give student teams early is the Design Review Checklist.
In a critique the protocol is three moves: observe, then question, then suggest. Never personal. Everything tied back to the FEES dimension under review and the strategic outcome you are trying to create. The designer responds, and together you make an action decision.
It sounds small. It is the difference between a team that gets sharper together and a team that stops saying what they think.
Practice, not permission
Each of the four capabilities asks for a different market, a different employer or a different problem to practise on. For years the fastest route ran through a manager willing to let you cross the silo — a lucky draw more than a plan, which is why the capabilities stayed concentrated in a small group of people.
That is the gate userOS is built to open. An AI Coach plus four iSWAT agents means you practise all four on your own first business, starting now, with the Coach challenging your thinking and keeping you accountable. The capabilities stay yours. What changes is the speed — and the fact that the practice starts today rather than when the right project appears.
Where to start
Pick up the one capability you have been circling around. Practise it on something real this month.
And the userOS pilot test waiting list is open now. The frameworks are yours. Go build something that matters.
Pick up the one capability you have been circling around. Practise it this month.
