Wake Up From Professional Autopilot

A weekly newsletter that uses psychology to help designers escape the execution trap — see your own patterns, read the room, speak the language of business, and build a career driven by intention.

Field notes on psychology & product strategy. No fluff. No Figma tutorials.

Every issue follows the same structure: a 3-minute video from the trenches, then a tactical essay you can use tomorrow at 9 AM.

The Autopilot Problem

Why designers default to reactive execution — and the attention patterns, cognitive traps, and borrowed workflows keeping them stuck.

Stakeholder Psychology

How PMs think, why engineers resist, and the behavioral science behind getting buy-in without formal authority.

Business-Fluent Design

Translating design decisions into the language of retention, risk, and revenue — the vocabulary that gets you heard in strategy meetings.

The Intentional Career

The psychological work of deciding who you want to become professionally — not just collecting frameworks, but building the identity to use them.

Recent issues

Blog cover image

Your Professionalism Is Actually Conflict Avoidance

Theres a personality trait that predicts career stagnation better than almost anything else — and most designers mistake it for a virtue. Its not imposter syndrome. Its not a lack of strategic skill. Its something quieter and harder to see. This issue is about the moment I sat in a design review, knew the PM was wrong, and said "sounds good" anyway.

Blog cover image

What Do You Actually Own When Engineers Can Ship Before You Finish?

Your engineering partner just shipped a feature before you finished the exploration phase. It doesnt look great, but it works. Your PM is happy. And youre sitting with a Figma file full of explorations nobody asked for. This issue asks the uncomfortable question every designer needs to answer: what do you actually own?

Blog cover image

"Show Me the Data" Is a Stall Tactic

Youve just presented a recommendation based on user interviews and heuristic analysis. The engineering lead says: "Interesting, but do you have quantitative data?" You dont — because the kind of data theyre asking for would require a six\-week experiment youll never get approved. This issue gives you the language to name the pattern and the playbook to respond.

Blog cover image

The Two Operating Systems Behind Every Designer`s Career

You've been at your company for two years. The work is fine. But youve started developing a story: design doesnt matter here. Your PM doesnt listen. Youve stopped trying new things because "whats the point?" This issue is about the two operating systems running underneath your career — and how to check which one you`re on.

Blog cover image

The Hidden Trap of Design Inspiration

You`ve spent 45 minutes collecting references. Your mood board looks incredible. You feel energized, creative, ready. Then you open the actual project file and something deflates. This issue explains why — and introduces a research-backed trick to make your brain stay hungry instead of satisfied.

Blog cover image

How to Debug Your Team Like an Engineer Debugs Code

Youre convinced your PM is the problem. Every sprint they override your decisions. Youve tried building rapport. You`ve tried being more assertive. Nothing changes. This issue introduces a model that changed how I diagnose every team friction I encounter — and it starts at the top, not the bottom.

Blog cover image

The Identity Crisis Hiding Behind "I Want to Be More Strategic"

Every mid-level designer says they want to "think more strategically." But what most of them actually mean is: give me better borrowed frameworks. Real strategic thinking requires something most people avoid — the willingness to not know. This issue is about the difference between collecting maps and learning to walk in the dark.

Blog cover image

Your Professionalism Is Actually Conflict Avoidance

Theres a personality trait that predicts career stagnation better than almost anything else — and most designers mistake it for a virtue. Its not imposter syndrome. Its not a lack of strategic skill. Its something quieter and harder to see. This issue is about the moment I sat in a design review, knew the PM was wrong, and said "sounds good" anyway.

Blog cover image

What Do You Actually Own When Engineers Can Ship Before You Finish?

Your engineering partner just shipped a feature before you finished the exploration phase. It doesnt look great, but it works. Your PM is happy. And youre sitting with a Figma file full of explorations nobody asked for. This issue asks the uncomfortable question every designer needs to answer: what do you actually own?

Blog cover image

"Show Me the Data" Is a Stall Tactic

Youve just presented a recommendation based on user interviews and heuristic analysis. The engineering lead says: "Interesting, but do you have quantitative data?" You dont — because the kind of data theyre asking for would require a six\-week experiment youll never get approved. This issue gives you the language to name the pattern and the playbook to respond.

Blog cover image

The Two Operating Systems Behind Every Designer`s Career

You've been at your company for two years. The work is fine. But youve started developing a story: design doesnt matter here. Your PM doesnt listen. Youve stopped trying new things because "whats the point?" This issue is about the two operating systems running underneath your career — and how to check which one you`re on.

Blog cover image

The Hidden Trap of Design Inspiration

You`ve spent 45 minutes collecting references. Your mood board looks incredible. You feel energized, creative, ready. Then you open the actual project file and something deflates. This issue explains why — and introduces a research-backed trick to make your brain stay hungry instead of satisfied.

Blog cover image

How to Debug Your Team Like an Engineer Debugs Code

Youre convinced your PM is the problem. Every sprint they override your decisions. Youve tried building rapport. You`ve tried being more assertive. Nothing changes. This issue introduces a model that changed how I diagnose every team friction I encounter — and it starts at the top, not the bottom.

Load more

Who writes this

I'm Stefan Vilar Markiewicz — a Product Design Manager based in Porto with a background in psychology. I've spent my career inside tech companies navigating the friction between design, product management, and engineering. I don't teach theory. I teach the patterns I see every day — in my own autopilot habits, in my team's dynamics, and in the gap between what designers know and what they communicate.

Get the best sent to your inbox, every month

Expect weekly detailed reads about new technologies, growing trends, and the latest developments with Web3.

Get the best sent to your inbox, every month

Expect weekly detailed reads about new technologies, growing trends, and the latest developments with Web3.

Get the best sent to your inbox, every month

Expect weekly detailed reads about new technologies, growing trends, and the latest developments with Web3.