A psychologist's field notes on working in tech.

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?

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.

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.

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.

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.

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.

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.