I lead design teams and run products of my own.
By day I run design at NewStore. At night I build my own products, end to end, that help people spend more time on what matters.
Products people use
on an ordinary Tuesday.
One thing at a time. Each product gets a run, gets finished, and then the next one starts. You can see the hand-off: red through the winter, teal across the summer, amber taking over in autumn.
- Commits
- 3,800
- Days with work
- 219
- Busiest day
- 102
Smaller things.
Built because something annoyed me.
Making people better is not a strategy.
It is the reason.
I want to help people get better at what they do. I believe the right tool can change what a person is capable of: make them faster, braver, free to focus on the work instead of the friction around it. That’s my mission, plainly stated: build things that help people do their best work and feel good doing it. Leading my design team is the same belief, pointed at the people doing the building.
The people you lead get a manager who noticed the pattern, instead of one who kept repeating it.
Dinner stops being a question somebody has to answer at six o’clock, every evening, for the rest of their life.
Everyone on your team opens what you made from one link, and nobody outside the company can.
Someone on a shop floor can answer the question while the customer is still standing there, instead of disappearing to go and check.
- Research rhythmEvery six weeks, whatever the roadmap does
- Story mappingOne narrative before anyone builds
- Feedback loopsThree horizons, not one
- MetricsOne owner per number, reviewed monthly
- OKRs and growthDiscipline, so creativity survives
- LevellingWhat good means, in writing
A team that works when I am not in the room.
My design operating system.
Years of leading design have taught me that a team scales on what is written down, not on who is in the room. Story mapping, a research rhythm, feedback loops, goals, levelling and metrics, each feeding company priorities, better products and growing people.
How each part worksWhatWeCook,
built from a phone, on parental leave.
A Mac mini at home running agents, a newborn asleep, and an app I had wanted to make for five years. Live Activities, widgets, Siri, and an import pipeline that watches the video when a reel has no recipe written on it.
Read how it was built See the product“It is hard to keep up with his ideas. I was still building the third one when he sent the sixth.”

He isn’t a typical design or UX lead. He can comfortably think like a product person, and is really on the cutting edge of generative AI and codegen, as his team all are too.
Outside NewStore, I build and I coach.
Products of my own, and help with yours.
Questions people ask.
What does Henning build?
I lead design teams at NewStore as Director of Design, where 70,000 store associates use what we make. I also run three products of my own: Intura, a leadership journal for people who lead, with a coach that has read every page; WhatWeCook, meal planning for households on the web and iOS; and ShareMyPage, for sharing pages you make with AI behind real access control.
Can I work with you?
Alongside NewStore, yes. Happy to talk: coaching people building their own products, taking yours apart with you and showing how I solved the part you are stuck on, or just a good conversation. The thirty minutes are free, and not a sales call. Book a time on the calendar at the bottom of the page or write to henning@hwa.design.
How do you build with AI?
I design the product and decide what gets built, and I build it with Claude Code. WhatWeCook was built in 32 days with Claude Code on a Mac mini at home, steered from my phone, on parental leave. The blog post tells the whole story.
Where are you based?
In Berlin, Germany, since 2015. Before that I spent six years in Erfurt, where I studied and in 2011 founded my own studio. I work in English and German, and my own products are built at home, on a Mac mini in my office in Berlin.



























