Over the past six months we've been running an experiment. We started sharing basic health knowledge with our team. Then financial knowledge. Then, somewhat ironically for a tech company, technology knowledge beyond their specific discipline. The hypothesis was simple: people who understand more of the world they operate in make better decisions. The results have been clear enough that we're formalising it into a framework.
What You Need to Know
- The Three Literacies framework covers health, financial, and technology literacy as interconnected professional capabilities
- Each literacy addresses a blind spot that causes real problems in enterprise delivery
- The framework is about contextual understanding, not expertise in each domain
- Teams with broader literacy make better trade-off decisions and communicate more effectively with stakeholders
The Framework
Technology professionals are deeply literate in their domain. That's table stakes. But the work they do exists in a context of human performance (health), commercial reality (financial), and technological breadth (tech beyond their specialism). Gaps in any of these areas lead to decisions that are technically sound but contextually wrong.
We've written about health literacy and financial literacy individually. This post brings them together with the third literacy and explains why they compound.
Health Literacy
The ability to understand and manage your own physical and mental wellbeing in the context of knowledge work.
This isn't about fitness programmes or wellness initiatives. It's about understanding that sleep deprivation impairs cognitive function. That sustained stress degrades decision-making. That physical movement improves focus. That screen fatigue is real and cumulative.
23%
decrease in problem-solving ability linked to chronic workplace stress
Source: American Psychological Association, Stress in America Report, 2019
A developer who recognises they're tired and takes a break before writing a critical piece of logic avoids a bug that would take hours to find later. A project lead who understands their own stress response catches themselves making a reactive decision and pauses. These aren't soft outcomes. They're operational improvements with measurable impact.
Financial Literacy
The ability to understand how business economics affect and are affected by technical decisions.
Not accounting. Not finance certifications. The practical understanding that a client's budget is finite, that time-to-market affects revenue, that infrastructure costs are recurring, and that the relationship between technical quality and business value is a trade-off, not an absolute.
We've seen developers make dramatically better scoping decisions after understanding how project economics work. The refactor that "only takes a week" looks different when you understand it comes from a budget that also needs to fund the features the client's board approved.
Technology Literacy (Beyond Your Specialism)
The ability to understand technology systems beyond your immediate discipline.
A frontend developer who understands database indexing makes different API design decisions. A designer who understands build performance budgets creates layouts that are feasible to implement efficiently. A project lead who understands deployment pipelines gives more realistic timelines.
Each literacy on its own is useful. That participation improves the quality of every decision.
Dr Tania Wolfgramm
Chief Research Officer
This isn't about making everyone a full-stack developer. It's about ensuring that each person has enough understanding of adjacent domains to participate meaningfully in cross-functional decisions. The designer doesn't need to write SQL. They need to understand what's expensive to query so they don't design a dashboard that brings the database to its knees.
Why They Compound
The three literacies aren't independent. They interact.
A team member who understands their health (recognises they're at capacity) and understands the financial context (knows the budget pressure) can have an honest conversation about trade-offs. "I can deliver this feature at high quality if I have five days. In three days, you'll get something that works but will need rework next sprint. Given the budget, which do you prefer?"
That conversation requires all three literacies. Health awareness to know your capacity honestly. Financial understanding to contextualise the options. Technical breadth to assess the quality trade-off. Without any one of those inputs, the conversation degrades into either "I'll just push through" (health gap), "take as long as you need" (financial gap), or "it'll be fine either way" (technical gap).
How We Implement It
The programme is lightweight. We're a small team. We can't run a university.
Monthly sessions. One per month, rotating between the three literacies. Twenty to thirty minutes. Practical, evidence-based, discussion-oriented. Not lectures.
Embedded in delivery. Sprint planning includes business context. Retrospectives include health check-ins. Technical discussions include cross-discipline participation. The literacies aren't separate from the work. They're woven into it.
Leader modelling. Leaders demonstrate the behaviour. Taking breaks visibly. Discussing budget constraints openly. Asking questions outside their specialism without embarrassment. The fastest way to build a literacy culture is for leadership to demonstrate that not knowing something isn't a weakness.
Evidence-based content. Tania's involvement ensures we're not sharing opinions dressed as facts. Every health claim is backed by research. Every financial principle is grounded in real economics. This rigour matters because the team will only trust the programme if the content is credible.
What We've Observed
Six months isn't long enough for definitive conclusions. It's long enough for patterns.
Sprint planning conversations are richer. Team members ask questions about business context that they didn't ask before. Estimation accuracy has improved, partly because people are more honest about their capacity and more aware of what their estimates mean financially.
The health practices have reduced the frequency of late-night work. Not to zero. But the team is more likely to recognise when they're running down and more likely to speak up about it. That cultural shift, from pushing through silently to flagging capacity openly, is the most valuable change.
Cross-discipline understanding has reduced friction between designers and developers. Fewer "this is impossible" reactions. More "how can we achieve the intent within the constraints" discussions. The conversations are more productive because both sides understand more of the other's context.
Where This Goes
The Three Literacies is a framework, not a curriculum. We're not prescribing specific content. We're establishing that these three domains matter for professional development in technology, and that investing in them produces better outcomes for the team and the clients.
We'll keep refining the programme. The content will evolve as we learn what lands and what doesn't. The structure might change. But the conviction is settled: developing the whole professional, not just their technical skills, is the highest-leverage investment a technology company can make.