How to Stay Human in a High-Pressure World – Podcast Stage | Craft 2026 (Panel Outline)

A podcast-stage panel on day two of Craft 2026’s first-ever podcast stage, hosted by the ABK Podcast (“Anonim Vezetői Klubja” / Leadership Anonymous, ~4 years old, founded to “make workplaces better in Hungary” after hearing people complain about bosses at Sunday family dinners — anonymous because “it’s not about who did what, but how we can be better next time”). Moderator: Fanni / Karolina Tóth (cognitive scientist → IT consultant → high-performance coach → scuba dive leader). Topic: mental health and IT leadership, based on their Hungarian episode #36 recorded just after Trump’s second-term win and the first AI-driven tech layoffs. Panelists: Marian Hartman (educator/consultant; creator of the Green Path method for behavior-first change management), Joseph Pelrine (psychologist, “retired,” Agile pioneer in Europe, worked on the Chrysler C3 team learning XP), and Kenny Schwegler (collaborative software design / socio-technical architecture enabler at Aardling/Agile e-commerce). Framing quote: Hungarian psychologist András Feldmár — “there are no mental-health issues, only problems in living.”

1. Opening — The State of Mental Health in Tech

1.1 Joseph — “the world is [messed] up”

• Perspective of “a 68-year-old who just had a heart attack” who wants to leave the world better by passing on his knowledge.
• Mental Health First Aid: a two-day training available in almost every country — just as you learned first aid/CPR for a driver’s license, learn how to act when you see someone ready to harm themselves. He did it last year and had to ask a friend “Are you planning on committing suicide?” — she said yes. “One little step we can all do to help others.”

1.2 Marian — don’t forget the actual work (the code base)

• Lots of effort now goes to mental-health resources, but people are exhausted — huge executive function spent just to live moment to moment.
• The forgotten baseline: the actual work. Asking engineers to work daily in “a really shitty code base” is like “asking them to smoke a pack of cigarettes a day on executive function.” Initiatives are important, but “don’t forget the code bases we’re working with.”

1.3 Kenny — humanity vs. checkboxing

• 14 years ago as a Java engineer, everything crashed on a Friday; 6 months in, he joked to a colleague about a glass of wine, she poured one, and a manager walked in — then poured himself a glass and sat down. Only later did Kenny learn the manager stayed just for them — that personal conversation (“you seem calm, how do you do that?”) is what helped.
• “I don’t feel like there’s time for that anymore.” Most mental-health efforts are checkboxing (“let’s implement this — but where is the humanity?”).
• His “boys get sad too” shirt (from the UK, supporting mental health) — in some UK workplaces asking “how was your day?” / talking about a bad day is dismissed as “woke”; men are constrained in what they should be without being asked what they want to be.
• Fanni: it’s easier to fall into rabbit holes as the world shrinks; “I can be unhappy with someone’s work and still appreciate their presence and give them feedback.”

2. What Makes a Tech Culture Toxic — Techno-Stress & Allostatic Load (Joseph)

2.1 What makes it good

• “Doing Extreme Programming right.”

2.2 Techno-stress — four components

• Techno-complexity — a constantly changing, complex technical environment (code bases, ever-faster AI generations, “every iPhone update I can’t find the buttons anymore”).
• Techno-overload — too many demands through technology, all “P0 urgency.”
• Techno-invasion — technology encroaching on personal life (“always-on” culture; a poll shows almost everyone sleeps with their phone by the bed — his tip: use a watch as the alarm instead).
• Status games disguised as meritocracy — “how many pull requests?”, employee-of-the-month.

2.3 Allostatic load

• McEwen’s allostatic load — constant wear and tear on brain and body when stress hormones never return to baseline.
• Eisenberger’s neuroimaging research — high stress makes the brain react the same way as to physical pain.

2.4 XP as safety, and the “Miranda card”

• Learned XP from the beginning on the Chrysler C3 team with Kent Beck, who said he invented XP “to make the world safe for programmers — and programmers safe for the world.”
• Ron Jeffries’ C3 “Miranda card” (like a US police Miranda card) — a developer’s rights: know what’s needed with clear priority; produce quality work at all times; ask for and receive help from peers/superiors/customers; make and update your own estimates in real units, not story points; accept responsibilities rather than have them assigned.
• Product-owner rights: an overall plan (what, when, cost); the most value out of each development week; see progress in an always-running system (XP’s goal: a system that runs by end of first sprint, even if it does nothing); prove it works via a repeatable test the PO specifies; change mind/substitute functionality/priorities; be informed of schedule changes and choose to reduce scope, restore the date, or cancel anytime and be left with a useful working system reflecting the investment to date.
• Context: late-90s pre-Y2K internet hype — companies aiming at IPOs wanted “something that just works enough,” and each week the customer could stop with a working system. “That’s safety.”

3. How Poorly Designed Systems Make People Sick (Kenny — Socio-Technical)

3.1 Optimize social and technical together

• In socio-technical systems, if you optimize the technical you must also optimize the social — they must improve together or you end up in a bad state. This is what’s happening with AI: it’s a technical tool, but we’re not looking at ways to improve the social part (his talk with Evelyn van Kelle).

3.2 The open-office study (Lean Agile Scotland talk)

• The original open office: teams sat together and designed the space to optimize their own needs (technical + social) → mental health up, production up, communication up, sickness down, cost down — a five-way win.
• Management consultants then copied it into other contexts → four of five went bad: mental health down (the one person in the corner watching everyone → less safety), sickness up (contagion, e.g., Corona), communication down (everyone in headphones because it’s noisy); only budget improved (cheaper).
• It works only where you include the people who work in it in the design — different teams need different things (e.g., a way to shut themselves off).
• Example: a workplace where every hour a group stood in front of a nearby meeting room → he went home to work, and communication went down.
• Also: digitalizing a process (e.g., DHL drivers of 20 years) can impact people who must cope with change they may not want — “we always think digitalization is good, but are we losing communication with people?”

4. Behavior-First Change — What Actually Works (Marian)

4.1 Smaller is better

• “Splash intervention effects” are exciting but don’t stick; affecting the day-to-day workflow is far more helpful, especially the invisible issues — and it’s different for every team.
• Example: management surveyed ~200 teams on handling a technical issue → ~175 different ways; one-shot fixes help some teams and hurt others. Be aware of each team’s workflow.

4.2 XP as a universal exception

• Some universal practices are wonderful — e.g., XP, because it produces a healthy code base via tiny behaviors, not a process (unlike Scrum, interpreted differently by every Scrum Master → inconsistency).
• Joseph: Kent called XP “a discipline of programming”; “we joked pair programming came about because nobody had the discipline to do it alone.” Scrum was originally a couple of XP practices (planning game, on-site customer); teams threw away the hard stuff (the highest-benefit part), leaving Scrum, then threw away reviews/iterations, ending in abused Kanban — “where many teams are right now.”
• Mandates (“everyone does Scrum now”) normally come from people who don’t have to do it themselves and only indirectly suffer.

4.3 Control as a basic need

• Fanni: the feeling of control is a basic safety need; being asked and having your response taken into account is one way people feel in control (not “organizing every Lego”).
• Kenny (open socio-technical theory): a top-down “command and control” does work; the research-backed open socio-technical (DP2) works ~40% better when taken seriously; the worst is laissez-faire — top does command-and-control but tells teams “you’re autonomous now” (a container word) → confusion. (He attributes the concept but can’t recall the researcher’s name.)

4.4 Practice + psychological safety must interweave

• Fanni: Scrum is measurable, but without psychological safety, being asked, autonomy, and control it’s “a pain in the bottom.” Safety and the right practices must connect in a figure-eight, not one-after-the-other — you can’t wait for everything to align before improving.

4.5 Understanding doesn’t change behavior — tiny nudges do

• Self-care is each person’s responsibility (she recommends Atomic Habits — “every human should read it”).
• For teams: let engineers identify the problems, and keep changes tiny — “nudges that take seconds or a minute” and don’t disrupt the work.
• Example: in refactoring, a “peel and slice” takes little time but lets you test previously untestable code — a huge difference from a tiny behavior. Such XP / “discipline of refactoring” practices raise engineering teams’ mental-health capacity.

5. Recovery, Not Downtime (Joseph)

5.1 Psychological detachment (Sonnentag/“Sonen Talken Fritz”)

• Four components: physical detachment from the work environment; relaxation techniques (mindfulness or “just having a beer”); mastery (do something you’re good at that isn’t coding); and control over your own time.

5.2 Restorative environments (Kaplan)

• Get into a natural environment, do low-demand activities (low physical/cognitive), and seek things with “soft fascination” (not fixating). He lives in an Alpine village of “200 people and 300 cows,” 2 minutes from the woods.
• “Rest is not a reward for completed work” — if you wait until you finish to rest, you’ll never finish (software never finishes). Build in rest and detachment periods; this counters the always-on techno-overload.

5.3 The privilege problem (Kenny) and rituals

• COVID made detachment worse for the less privileged — people working and eating at the same dining table with no separate space. If you want people working from home, ensure they have separate spaces to work and live.
• Joseph’s YouTube talk “Love in the Time of Corona” — the cognitive dissonance of virtual environments (cameras off / virtual backgrounds to defend personal space or hide a crowded flat).
• Rituals: a Dutch anthropologist’s small habit — take your briefcase, walk 20 minutes, come back, then start work (and repeat at day’s end) to ritually detach. Joseph meditates 10 minutes in his garden each morning (“I can always tell when I don’t”).
• Leaders must recognize invisible load (e.g., email — thankless, invisible unless unanswered); a 7 a.m. meeting plus 2 hours of email means asking people to get up at 5.

6. Closing Tips (“shooting match”)

6.1 Marian

• Don’t do an intervention — whether AI or parking spaces. Focus on something small and practical in the workflow and see where it goes; for AI adoption, “starting with a very tiny habit in the workflow will get you farther faster and not stress people out.”

6.2 Kenny (deep democracy)

• However you decide (autocratic or democratic), once there’s a decision, ask those who were against it how it is for them, let them rant / be uncomfortable with them, then ask “what do you need to go along?” — a deep democracy tip. People end up saying “even though you didn’t take my advice, I’m fine because you listened to me / cared for me.” “Let’s get comfortable with being uncomfortable.”

6.3 Joseph (the “leader” tape metaphor)

• On a reel-to-reel tape, the blank clear part at the start that holds no information and can’t be recorded onto is called the “leader.” “Think about it.”

6.4 Host’s close

• The point was to bring ourselves back to ourselves and to caring for our teams — ”AI is not going to do that, and we can’t ask it to”; support each other via practices like XP and change implemented so people feel in control.

People & References Cited

• Fanni / Karolina Tóth — moderator; ABK Podcast (Leadership Anonymous).
• Marian Hartman — Green Path method / behavior-first change.
• Joseph Pelrine — psychologist; Agile pioneer; Chrysler C3 / XP; “Love in the Time of Corona.”
• Kenny Schwegler — socio-technical architecture; talk with Evelyn van Kelle.
• András Feldmár — “no mental-health issues, only problems in living.”
• Kent Beck — XP (“make the world safe for programmers”), “discipline of programming.”
• Ron Jeffries — the C3 “Miranda card” of developer/product-owner rights.
• McEwen — allostatic load. Eisenberger — stress-as-physical-pain neuroimaging. Sonnentag — psychological detachment. Kaplan — restorative environments / soft fascination.
• Book: Atomic Habits. Concepts: Mental Health First Aid, techno-stress (complexity/overload/invasion/status games), XP, Scrum→Kanban degradation, socio-technical DP2 vs. laissez-faire, open-office study (Lean Agile Scotland), peel-and-slice refactoring, deep democracy, recovery vs. downtime.
• Companies mentioned: DHL (drivers), Chrysler (C3).

Video: https://www.youtube.com/watch?v=Yq9cx4E-zU8 — Transcript via yt-transcript.sh; outline generated from the transcript.