Team Lead Product/SIMStation/Vienna, Austria
I turncomplex productsinto clearexperiences.
Product leader, technically grounded, focused on building products that work for users, teams and businesses.
Philipp Kogler is a product leader with a strong software engineering background who turns complex technical products into clear, usable and commercially valuable experiences.
Selected work
A few problems worth making clear.
Case studies from product leadership at SIMStation and the path that led there — written to be honest about role and approach rather than dressed up with invented numbers.
About
From building software to building the product around it.
Team Lead Product
SIMStation
Vienna, Austria
I started in software development and frontend engineering, and spent years close to the code — shipping interfaces, owning frontend architecture, and learning how technical decisions shape what a product can become.
Over time my focus widened from implementation to the questions around it: what to build, for whom, and why. That path led through frontend leadership into product management and, today, product leadership at SIMStation.
I care about complex systems and the discipline of making them understandable. Good products rarely come from a single function working alone — they come from customers, design, engineering and business pulling in the same direction. My job is mostly to create the clarity that lets that happen.
I try to keep the writing on this site honest: confident where I have earned it, broad where the detail belongs in a conversation rather than a portfolio.
Design, technology and product as one connected discipline.
Experience
From writing the software to leading the product.
The same arc, told as a path: implementation gradually giving way to broader product and organisational responsibility.
- Implementation
Software Developer
Writing production software and learning how technical decisions ripple through a product long after the code ships.
- Implementation
Frontend Engineer
Building the interfaces users actually touch — turning requirements into usable, reliable, maintainable front ends.
- Ownership
Head of Frontend
Owning frontend architecture and direction, and starting to shape not just how things were built but what was worth building.
- Ownership
Product Manager
Moving fully into the product discipline — discovery, prioritisation, roadmap and the alignment work that connects teams to outcomes.
- Leadership
Team Lead Product
SIMStation
Leading product at SIMStation: strategy, discovery, portfolio and the organisational structure that lets product, design and engineering do their best work.
Capabilities
What I actually do, and how.
No progress bars. Just the areas I work in and a plain description of what each looks like in practice.
Product Strategy
01Connecting where a product should go with what the business needs and what is technically realistic — then making that direction legible to everyone who has to act on it.
Product Discovery
02Separating the requested feature from the underlying problem, and validating what is worth building before committing engineering effort to it.
Roadmapping & Prioritisation
03Turning a noisy backlog of ideas into a sequenced plan people trust — balancing impact, effort, risk and strategic alignment.
UX & Product Design
04Shaping flows and interfaces so that complex, high-stakes workflows feel clear and controllable for the people using them.
Technical Product Leadership
05Using a real engineering background to make better trade-offs, ask sharper questions, and keep product and architecture decisions honest with each other.
Stakeholder Alignment
06Getting product, design, engineering, commercial and customer perspectives to a shared understanding — and keeping them there as reality changes.
Product Operations
07Designing the processes, rituals and structures that let a product organisation make decisions consistently without drowning in bureaucracy.
Team Development
08Growing people and the environment around them, so ownership and good judgement are distributed rather than bottlenecked.
Software Engineering
09The foundation everything else is built on — years close to the code, which still shapes how I read feasibility, risk and quality.
Data-Informed Decision-Making
10Using evidence to steer decisions without pretending numbers remove the need for judgement about what actually matters.
How I think
Scattered signals, shaped into clear decisions.
Working approach
Six principles I keep coming back to.
Start with the problem, not the requested feature
The first ask is rarely the real need. Understanding the problem beneath it is where most of the value is created.
Make complexity understandable
Complex systems are unavoidable in this domain. Making them legible — to teams, customers and stakeholders — is the actual work.
Connect user value, business value and technical reality
A good decision holds all three at once. Optimising for one while ignoring the others is how products quietly go wrong.
Create systems that help teams make better decisions
The highest-leverage output is usually not a feature but the structure that lets a team decide well, repeatedly, without me in the room.
Build enough structure to create clarity — not bureaucracy
Process should reduce ambiguity, not add ceremony. The goal is clarity with the least structure that achieves it.
Treat design, technology and product as one connected discipline
They are not separate departments handing off artefacts. The best results come when they are reasoned about together.
Off the roadmap
A few things beyond the work.
Vienna
Home base. A city that takes craft and quiet quality seriously — which suits how I like to work.
Medical simulation
The domain I work in: helping clinicians train and debrief in realistic, high-stakes scenarios without the real-world risk.
Guitar
A long-running way to think with my hands and step away from screens.
Building useful things
Side experiments, small tools, and the occasional over-engineered solution to a very small problem.
The point
Goodproductsrarelyfailoncode.Theyfailonclarity.Myworkistomakethecomplexunderstandable,alignthepeoplearoundit,andturnscatteredintentintodecisionsateamcanacton—together.