Daryl Robertson

Impact

Building better engineering organizations

I believe effective engineering leadership should produce meaningful, measurable improvements in how teams work, how people grow, and what an organization can accomplish.

Throughout my career, I have focused on identifying opportunities for improvement, understanding the underlying challenges, and working with teams to create sustainable solutions.

Sometimes the results are technical. Sometimes they involve processes, culture, or professional development. Often, the most meaningful improvements involve all of them.

The following examples reflect some of the work I am most proud of.

Engineering Quality of Life

Improving team health through data, feedback, and continuous improvement

  • 36% improvement in team health

Healthy engineering teams do not happen by accident. They require deliberate attention, honest feedback, and a willingness to challenge established ways of working.

One of the initiatives I am particularly proud of involved taking a more structured, data-driven approach to engineering Quality of Life (QOL).

The idea was straightforward: if we wanted to improve the experience of being an engineer, we needed to understand that experience from the perspective of the people doing the work.

Understanding the problem

Traditional measures of engineering success tend to emphasize delivery, productivity, and technical outcomes.

Those measures matter, but they do not tell the entire story.

They may not reveal whether engineers feel supported, whether development processes create unnecessary friction, whether technical challenges are becoming persistent frustrations, or whether people believe their careers are progressing.

I wanted to understand those less visible factors and create a more consistent way to identify opportunities for improvement.

An iterative approach

Rather than relying exclusively on intuition or occasional conversations, I introduced a more deliberate approach to gathering feedback, examining patterns, and identifying areas where changes could make a meaningful difference.

The emphasis was on continuous improvement rather than sweeping transformation.

Listen to the people experiencing the problems. Understand the underlying causes. Make thoughtful changes. Evaluate whether those changes helped. Repeat.

An important part of this approach was recognizing that improvements to team health and engineering effectiveness should reinforce one another.

The outcome

36% improvement in team health

The initiative demonstrated that the engineering experience could be improved through consistent attention, measurement, and incremental change.

More importantly, it reinforced a principle that continues to inform my leadership approach: the health of an engineering organization deserves the same deliberate attention as the software it produces.

Related reading: A Data-Driven, Iterative Approach to Culture and Well-Being

Investing in Professional Development

Making career growth part of everyday engineering culture

  • 3.67 → 9.33 / 10

Professional development is one of the areas where I believe engineering organizations frequently fall short.

Most companies recognize its importance, but good intentions do not always translate into consistent practices.

Development goals can lose momentum between performance reviews. Career conversations become reactive. Engineers may struggle to understand what growth looks like or whether their organization is genuinely invested in helping them achieve it.

Creating a more intentional approach

I believe professional development needs structure, consistency, and meaningful engagement from leadership.

That means taking time to understand individual strengths, interests, and aspirations, helping people identify realistic opportunities for growth, and ensuring those conversations continue throughout the year.

It also means recognizing that professional growth is not synonymous with promotion.

Growth may involve deeper technical expertise, stronger collaboration, increased confidence, broader responsibilities, or the development of entirely new capabilities.

The outcome

Professional development experience: 3.67 to 9.33 out of 10

This improvement in team-reported professional development experience demonstrated the difference that deliberate attention and consistent support can make.

It is also one of the experiences that reinforced my interest in creating better tools and processes for career development.

I want the people I lead to know that their growth matters, and I believe it is my responsibility to make that commitment visible through action.

Explore Paragon

Scaling a Cross-Platform Design System

Technical leadership through collaboration, alignment, and shared ownership

  • 9 engineers directly led
  • 16-person cross-functional team
  • 12 engineering teams supported
  • Android, iOS, and Web

I led nine engineers within a 16-person, cross-functional design system team, working closely with product and design leadership to develop and maintain a shared design system supporting 12 engineering teams across three platforms.

The technical challenges of creating reusable components were significant, but the broader leadership challenges were equally important.

A design system cannot succeed through component development alone. It also requires alignment between disciplines, trust from the teams consuming it, and practices that make adoption and contribution sustainable.

Beyond the component library

My responsibilities extended beyond the technical implementation of the design system.

The work involved establishing engineering practices, managing technical priorities, supporting collaboration between disciplines, and creating an environment where engineers could contribute effectively.

It also meant balancing the needs of multiple consuming teams while maintaining a coherent technical direction.

Making the system work at scale

A shared engineering platform becomes valuable when teams can depend on it.

That requires consistent delivery, clear expectations, good communication, and an understanding of the practical challenges faced by the engineers using it.

My focus was on building the engineering organization and working relationships needed to support those requirements.

What this demonstrated

The experience reinforced my belief that effective technical leadership is as much about people and organizational systems as it is about architecture and code.

Strong engineering practices, collaborative relationships, and shared ownership are not secondary concerns. They are essential to making complex initiatives successful at scale.

What ties these experiences together

Although these initiatives addressed different challenges, they reflect a consistent approach to engineering leadership.

I believe in looking beyond immediate symptoms to understand the systems behind them.

I believe in listening carefully to the people doing the work, using meaningful feedback to guide decisions, and being willing to challenge practices that no longer serve their purpose.

I believe that investing in people and improving how teams operate leads to better engineering outcomes.

Most importantly, I believe that improvement is an ongoing responsibility, not a one-time initiative.

Good engineering leadership requires continuous attention to the people, processes, and tools that make great work possible.

More about my leadership philosophy

Further reading