The Research That Should Change How Tech Teams Are Managed
Ask most engineering managers or team leads what drives developer motivation and creativity, and you will likely hear a familiar list: competitive salaries, public recognition, stock options, flexible hours. These feel like obvious answers because they are the levers managers most commonly reach for. But a landmark body of research tells a different story — one with significant implications for how technology teams, privacy-focused organisations, and knowledge-work businesses are structured and led.
After analysing nearly 12,000 daily diary entries submitted by 238 workers across a range of knowledge-intensive roles, researchers discovered that the single most powerful driver of positive emotion, motivation, and creative output was not pay, not praise, and not perks. It was something far quieter: making meaningful progress on work that actually mattered. The finding, which challenges decades of management orthodoxy, has particular relevance for the technology sector, where organisations routinely struggle with retention, burnout, and the kind of deep creative work that powers innovation in areas such as open-source development, cybersecurity, and privacy engineering.
The research, widely known as the "Progress Principle," was pioneered by Harvard Business School professor Teresa Amabile and researcher Steven Kramer. Their methodology was unusually rigorous by management-research standards: participants submitted structured daily diary entries over extended periods, giving researchers a granular, real-time view of how daily events at work shaped mood, motivation, and creative thinking. The dataset of nearly 12,000 entries provided a level of longitudinal depth rarely seen in workplace studies, as Silicon Canals reported.
What "Meaningful Progress" Really Means for Developers and Privacy Professionals
For developers, security researchers, data protection officers, and the broader community of technology professionals, the Progress Principle lands with particular force. Knowledge work in these fields is often invisible. A developer who spends three days eliminating a critical security vulnerability has accomplished something significant, but the output is absence rather than presence — a breach that did not happen, a compliance audit that passed cleanly. Privacy professionals who implement GDPR-compliant data architectures rarely receive a standing ovation. Infrastructure engineers who migrate workloads to sovereign cloud environments solve complex, consequential problems that most stakeholders never fully understand.
This invisibility creates a structural risk. When meaningful work goes unrecognised — not through deliberate neglect, but simply because management focuses on the wrong metrics — the motivational machinery quietly breaks down. Amabile and Kramer's research quantified this with uncomfortable precision. On days when workers recorded forward movement on meaningful tasks, they reported the highest levels of positive emotion and intrinsic motivation. On days when progress was blocked — by unclear priorities, bureaucratic obstruction, or last-minute changes of direction — motivation and creativity dropped sharply, and those effects often persisted into the following day.
A related body of evidence from Harvard Business Review reinforces these findings. In surveys of managers, researchers asked them to rank the factors most likely to motivate workers on a given day. Recognition came top. Pay incentives ranked highly. Progress on meaningful work finished last. The gap between what managers believe motivates people and what actually does is not merely academic — in fast-moving technology environments, it translates directly into higher attrition, lower code quality, and a diminished capacity for the deep, sustained creative work that security and privacy engineering demands.
Catalysts, Blockers, and Why Sprint Planning Matters More Than You Think
The research identifies two categories of managerial action that directly shape whether workers experience progress or stagnation. "Catalysts" are actions that directly enable progress: setting clear goals, providing the autonomy to approach problems creatively, ensuring adequate resources, and protecting teams from unnecessary interruptions. "Inhibitors" — or what the researchers call "blockers" — are the opposite: vague or constantly shifting objectives, excessive meetings, unclear ownership, and the kind of organisational friction that consumes time without producing outcomes.
For technology organisations in Europe navigating complex regulatory terrain — GDPR compliance cycles, NIS2 implementation, AI Act obligations — the relevance is immediate. Regulatory work has a particular tendency to generate the conditions that destroy motivation: ambiguous requirements, externally imposed deadlines, stakeholder pressure, and outcomes that are difficult to measure. A data protection officer who spends weeks preparing a data protection impact assessment, only to have the project scope change fundamentally before sign-off, has experienced a textbook progress blocker. The emotional and motivational cost, according to the diary-entry research, is real and measurable.
"The main thing is to make the main thing the main thing. When we protect people's time and focus, we are not just being kind — we are directly enabling the progress that drives everything else."
— Teresa Amabile, Harvard Business School (paraphrased from Progress Principle research)Agile methodologies, widely adopted in software development, inadvertently encode some of the Progress Principle's insights. Sprint-based structures break large projects into visible, completable units of work — precisely the kind of incremental progress the research identifies as motivationally potent. When a sprint ends with a working feature deployed, a security patch shipped, or a compliance control documented and tested, the team registers a concrete win. According to research from McKinsey, organisations that give knowledge workers clear, achievable near-term milestones consistently outperform those that rely on annual goal-setting and infrequent review cycles.
How Remote and Distributed Teams Amplify the Progress Problem
The shift to remote and hybrid working models — accelerated by the pandemic and now deeply embedded in European technology culture — has made the progress problem more acute. In a co-located office, informal signals of progress are pervasive: overheard conversations, visible whiteboards, the social cues of a team shipping work. Remote environments strip these signals away. A developer working from home on a distributed open-source project may be making extraordinary progress but receive almost no external validation of that fact.
Research from Gallup on employee engagement consistently finds that remote workers who feel their work is meaningful and that they are making progress report higher engagement scores than their office-based counterparts — but remote workers who lack that sense of meaningful progress show the steepest disengagement drops. The implication for technology team leaders is clear: in distributed environments, making progress visible requires deliberate, structured effort. It does not happen automatically.
This is one reason why practices like asynchronous stand-ups, documented decision logs, and visible issue trackers — common in privacy-conscious open-source communities that use self-hosted tools over cloud-based alternatives — may have motivational benefits beyond their obvious operational utility. When a contributor can see a closed pull request, a resolved issue, or a completed audit trail, they have tangible evidence of their own forward movement. The tool choice is not neutral: organisations that prioritise digital sovereignty and deploy open-source project management infrastructure are, perhaps inadvertently, also creating the conditions the Progress Principle identifies as motivationally essential.
What the Data Tells Tech Leaders to Actually Do Differently
Translating research findings into management practice is where most organisational improvement efforts stall. The Progress Principle, however, offers unusually concrete guidance. Because the research identified specific event types that corresponded with positive and negative inner work life, it is possible to construct a practical framework for technology team leadership.
| Management Action | Effect on Progress | Relevance for Tech Teams |
|---|---|---|
| Set clear, stable goals | Strong catalyst | Reduces scope creep in security and compliance projects |
| Remove bureaucratic blockers | Strong catalyst | Speeds up deployment cycles and audit workflows |
| Grant autonomy on approach | Moderate catalyst | Critical for creative problem-solving in open-source and privacy engineering |
| Provide resources and information | Moderate catalyst | Reduces context-switching and unblocks stalled work |
| Recognise small wins explicitly | Amplifies progress effect | Particularly important in invisible-output roles (security, infrastructure) |
| Change priorities without explanation | Strong blocker | Major source of developer frustration in agile environments |
| Create unclear ownership | Strong blocker | Particularly damaging in compliance and cross-functional projects |
The data also carries a warning for organisations that over-invest in extrinsic rewards at the expense of removing structural blockers. A generous bonus delivered at the end of a quarter in which a developer felt constantly obstructed, under-resourced, and disconnected from meaningful outcomes may produce short-term satisfaction but will not repair the motivational damage. According to research published by the American Psychological Association, intrinsic motivation — the kind generated by meaningful progress — is far more durable and predictive of long-term performance than extrinsic incentives. When extrinsic rewards become the primary motivational strategy, they can actually crowd out intrinsic motivation over time, a phenomenon psychologists call "overjustification."
