Organizational Dysfunctions: Trond Hjorteland (Part 2)

The podcast discusses widespread workplace disengagement, framing "quiet quitting" as a rational response to environments that fail to meet employees' psychological needs for autonomy, purpose, and involvement. It critiques the overemphasis on rigid frameworks like Agile, Scrum, DORA, and OKRs, which are often misapplied as prescriptive rules rather than principle-based guides. This top-down enforcement leads to metrics manipulation, burnout, and organizational dysfunction, particularly in hierarchical structures (DP1), where performance indicators become meaningless targets instead of tools for improvement.

In contrast, the discussion advocates for adaptive, context-sensitive approaches grounded in Open Systems Theory, emphasizing self-managing teams (DP2) that design their own processes and embrace participatory change. These teams naturally generate meaningful metrics and are more resilient to challenges like AI integration, which can either erode skills and cause job insecurity in DP1 settings or enhance capabilities in DP2 environments. The conversation underscores that sustainable performance comes not from control and efficiency metrics, but from empowering teams, aligning work with personal purpose, and recognizing the interconnected feedback loop between fulfilling work and overall well-being.

• What if you stopped chasing DORA metrics and built your own feedback loop instead?

  • Move: Replace external metric dashboards with a personal weekly review system tracking only three self-defined outcomes (e.g., code quality, user impact, learning). Use AI to summarize pull requests, support tickets, and usage logs into insights.
  • Why Now?: Blind adoption of DORA metrics without control leads to misaligned incentives and burnout - especially for solo developers pressured to "perform." You're the only one who can define what success means in your context.
  • Expected Upside: Regain autonomy, reduce noise, and align work with actual value delivery. This builds sustainable momentum by focusing on meaningful progress over vanity metrics.

• What if you treated every AI tool as a team member you must train - not just a shortcut?

  • Move: Dedicate 30 minutes daily to refine prompts, audit AI-generated outputs (code, copy, designs), and document edge cases where it fails. Treat this like onboarding a junior developer: give feedback, set boundaries, and integrate it into your workflow deliberately.
  • Why Now?: Unchecked reliance on AI erodes critical thinking and makes your skills replaceable (DP1 risk). With AI already embedded in tools you use, intentional stewardship today prevents deskilling tomorrow.
  • Expected Upside: Transform AI from a threat to a force multiplier. You maintain ownership of judgment and design, preserving your irreplaceability while boosting output quality.

• What if you redesigned your work structure using participative design - starting with yourself?

  • Move: Spend one weekend running a solo version of a Participative Design Workshop: map your current workflow, identify pain points ("hallway complaints" you'd tell others), then prototype a new structure (e.g., time-blocking, modular projects, decision filters) that gives you control over coordination and feedback.
  • Why Now?: Top-down frameworks fail because they ignore context. As a solo operator, you have full agency to recontextualize principles (Agile, Team Topologies) into something that fits your reality - before burnout or disengagement sets in.
  • Expected Upside: Escape the "quiet quitting" spiral by creating a self-sustaining system where work feels purposeful, adaptive, and aligned with your psychological needs - autonomy, competence, and relatedness.

• Audit and remove vanity metrics from your workflow; only track DORA-style indicators (e.g., deployment frequency, MTTR) if you've implemented their underlying enablers like modular code and automated recovery.
• Design your software projects with DP2 principles by building self-contained, full-stack features that reduce dependencies and increase autonomy over time.
• Avoid adopting popular frameworks (e.g., Scrum, Team Topologies) verbatim; instead, extract their core principles and adapt them to your solo context through iterative experimentation.
• Use AI tools like Copilot or Claude as assistants for ideation and scaffolding, but enforce a strict review process to preserve critical thinking and avoid skill erosion.
• Implement regular personal retrospectives using a feedback loop: define one goal, measure progress qualitatively/quantitatively, reflect weekly, and adjust - without external reporting pressure.