> Markdown version of [/videos/1412-hidden-efficiency-how-to-enable-your-non-engineers-as-a-cto](https://www.wearedevelopers.com/videos/1412-hidden-efficiency-how-to-enable-your-non-engineers-as-a-cto). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Hidden efficiency - How to enable your non-engineers as a CTO

Over 90% of experimental tech initiatives never require hard-coding. Discover how CTOs unlock hidden organizational efficiency by empowering non-engineers to build low-code workflows.

- **Speakers:** [Andi Stryz](https://www.wearedevelopers.com/@andi-stryz)
- **Event:** World Congress 2025
- **Published:** August 20, 2025
- **Duration:** 24:40
- **URL:** https://www.wearedevelopers.com/videos/1412-hidden-efficiency-how-to-enable-your-non-engineers-as-a-cto

## Summary

Traditionally, engineering leadership focuses on department-level efficiency metrics like DORA, but true leverage lies in prioritizing company-wide operational efficiency. A CTO's primary focus should be the organization's overarching health, tracking ultimate outcomes like annual recurring revenue (ARR) per full-time employee. Adopting the "team number one" principle—where cross-functional executive peers are prioritized over direct reports—prevents departmental lobbying and ensures leadership decisions consistently serve the greater corporate good.

To unlock organizational scale, engineering departments must shed repetitive tasks and unpredictable operational requests. This requires adopting a strict "buy commodities, build assets" mindset: using established SaaS for generic needs, hard-coding only mission-critical business logic, and deploying low-code platforms like Retool for customized internal tools. Introducing a dedicated "business automation manager" role, embedded directly within Scrum teams, further bridges the operational gap. These non-technical specialists handle peripheral workflows so software engineers can remain relentlessly focused on technical challenges.

At the execution level, treating process automation as an accessible commodity revolutionizes daily operations. By empowering non-engineers with no-code tools to execute initial data migrations, build customized dashboards, or handle rapid partner integrations, teams adhere to the operational mantra: "do it once, do it twice, automate it." Rather than immediately assigning developers to untested initiatives, organizations should leverage zero-code platforms for any project with unknown complexity. Strikingly, over 90% of these experimental concepts never require a hard-code phase, proving that radical delegation to non-technical staff is an extraordinary hidden efficiency booster.

**Keywords:** engineering efficiency KPIs, ARR per FTE metric, team number one principle, cross-functional alignment, buy vs build methodology, low-code internal tooling, no-code process automation, business automation manager, DORA metrics prioritization, SaaS commodity tools, Retool application development, API integration automation, workflow automation platforms, organizational scaling metrics, CTO operational strategy

## Chapters

1. **Overview of the speaker and company background** (00:12) — How the speaker's technical background supports operational growth at the Finn car subscription service.
1. **Reevaluating traditional software engineering efficiency metrics** (03:07) — Standard engineering performance indicators often optimize departmental operations instead of addressing the needs of the whole company.
1. **Keeping routine tasks away from software engineering teams** (05:30) — Relocating repetitive workflows or vaguely defined initiatives to non-technical roles improves engineering focus and overall morale.
1. **Prioritizing overall company efficiency over departmental operations** (07:32) — Using revenue per employee as a primary metric aligns technology decisions with broader business operations.
1. **Core strategies for unlocking operational efficiency at scale** (11:31) — Three foundational pillars for scaling organizational growth include team alignment, acquiring ready-made commodities, and automating structured processes.
1. **Applying the team number one leadership principle** (13:38) — Executives must prioritize their peer leadership team over their direct reports to prevent destructive departmental silos.
1. **Leveraging low-code frameworks to empower non-technical roles** (16:08) — Providing role-specific internal applications allows business automation managers and operational staff to build functional solutions independently.
1. **Scaling process automation to eliminate manual workflows** (19:50) — Widespread adoption of no-code automation removes tedious chores from engineering and significantly accelerates third-party integrations.
1. **Managing unknown project complexity with no-code pilots** (22:28) — Proactively validating business challenges using pilot solutions prevents resource drain before committing to full custom engineering.

## Related Moments

- [Addressing automation anxiety and prioritizing impactful engineering work](https://www.wearedevelopers.com/videos/100123-agentic-employees-in-world-s-most-downloaded-fintech-app) (from "Agentic employees in world's most downloaded FinTech app")
- [Summarizing the organizational benefits of platform engineering](https://www.wearedevelopers.com/videos/885-platform-engineering-vs-devops-why-not-both) (from "Platform Engineering vs. DevOps Why not both?")
- [Learning operational efficiency from small and medium software companies](https://www.wearedevelopers.com/videos/1346-wearedevelopers-live-blockchain-after-the-hype-vibing-all-the-things-big-tech-and-work-best-practices-more) (from "WeAreDevelopers LIVE - Blockchain after the hype, Vibing all the Things, Big Tech and Work Best Practices & more")
- [Overcoming executive FOMO and driving meaningful process change](https://www.wearedevelopers.com/videos/100266-ai-won-t-fix-your-engineering-culture) (from "AI Won't Fix Your Engineering Culture")
- [Addressing developer productivity challenges with internal tooling](https://www.wearedevelopers.com/videos/1118-developer-experience-in-the-age-of-ai) (from "Developer Experience in the Age of AI")
- [Key takeaways on motivating engineering teams](https://www.wearedevelopers.com/videos/373-seriously-gaming-your-cloud-expertise-from-cloud-tourist-to-cloud-native) (from "Seriously gaming your cloud expertise: from cloud tourist to cloud native")

## Related Articles

- [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development)
- [Exploring AI: Opportunities and Risks for Developers](https://www.wearedevelopers.com/magazine/522-exploring-ai-opportunities-and-risks-for-developers)
- [Transforming Software Development: The Role of AI and Developer Tools](https://www.wearedevelopers.com/magazine/527-transforming-software-development-the-role-of-ai-and-developer-tools)
- [Why developer experience matters](https://www.wearedevelopers.com/magazine/514-why-developer-experience-matters)

## Related Jobs

- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [Principal Software Engineer, Enterprise AI Platform](https://www.wearedevelopers.com/jobs/ext/1467292-principal-software-engineer-enterprise-ai-platform) at **GitHub**
- [Senior Software Engineer, Enterprise Products](https://www.wearedevelopers.com/jobs/ext/1841248-senior-software-engineer-enterprise-products) at **GitHub**
- [Senior Engineer, Infrastructure Platform](https://www.wearedevelopers.com/jobs/ext/328836-senior-engineer-infrastructure-platform) at **Intercom, Inc.**
- [Staff Software Engineer, Copilot Experiences](https://www.wearedevelopers.com/jobs/ext/164361-staff-software-engineer-copilot-experiences) at **GitHub**
- [Director, Software Engineering](https://www.wearedevelopers.com/jobs/ext/186599-director-software-engineering) at **Twilio**