Design in tech used to be simple. A few designers, a shared room, and a list of wireframes to draw. But as software development scaled through agile methodologies and B2B digital transformation, design found itself embedded deep within engineering-driven organizations.
At dti digital, a Brazilian digital transformation firm founded in 2009, design grew from an emerging discipline into a core operational pillar. Supporting dozens of major clients globally with over 75 digital product designers, the team faced a classic growth problem: How do you structure, nurture, and support designers across their career journey in an agile, multi-client environment?
Here is what I learned from analyzing, interviewing, and refactoring our design practice from the inside out.
The Unspoken Disconnect in Agile Product Teams
When an agency or consulting firm grows rapidly—adding dozens of designers in a matter of months—operational friction is inevitable. To understand where the machine was breaking down, I conducted quantitative surveys (with 82 participants, including one-third of the design team at the time) and qualitative focus groups across key roles: designers, tech managers, product owners, and developers.
The findings exposed a clear gap between design theory and daily operational reality:
- The Feedback Vacuum: 50% of junior and less experienced designers reported receiving no structured feedback loops or personal career tracking.
- Role Ambiguity: Leadership roles (TMs, POs, SMs) frequently assigned pure management or product tasks to designers, blurring the scope of the craft.
- Client Friction vs. Validation: While design methodology was valued internally, client misunderstanding directly crippled user research and testing. Only 32% of designers were able to run regular usability tests, and only when the client possessed a baseline understanding of UX values.
- First Impressions Matter: Onboarding presentations had a massive impact—67.3% of team members who attended introductory design sessions correctly understood the actual role and responsibilities of a product designer.
Personas Beyond Job Titles
In a team of 75+ designers, a generic career ladder doesn’t work. By analyzing the day-to-day journey of the team, I mapped out distinct sub-personas:
- The Intern / Junior: Recently onboarded, hungry for guidance, but often navigating projects without clear internal reference points.
- The Mid-Level (Pleno): Seasoned in execution, looking to deepen product strategy skills, but stuck between execution pressure and client pushback.
- The Senior / Lead: Deeply experienced, occupying Chapter leadership roles, with a strong desire to mentor and elevate the craft across the broader organization.
When you view your team through this lens, you realize that design ops isn’t just about Figma libraries or process documentation—it’s about removing friction for real human beings at different stages of their craft.
“What is DesignOps? The tool, the grease, and the tracks that amplify the value of a design team.” — Dave Malouf
The Shared Principles: Defining Our Craft
To align non-designers and protect the integrity of the work, I established a set of north-star principles. These were not inspirational posters for the office wall; they were explicit boundaries and definitions meant to empower designers when negotiating scope with clients and product managers:
- People & Interactions First: True agile design prioritizes real human collaboration, empathy, and active listening over rigid documentation and toolchains.
- Design is Strategy, Not Just Aesthetics: The work begins long before the UI stage. If a designer is only brought in to “make it look good,” the process is already broken.
- Research & Validation are Non-Negotiable: Usability testing and user research are core components of risk mitigation, not optional luxuries to cut when deadlines get tight.
- Autonomy Requires Context: Designers perform best when given business context and problem statements, not rigid specification lists handed down as orders.
- Continuous Growth Over Isolated Execution: A designer’s trajectory within a team must be supported by structured mentorship and active community feedback loops.
From Process to People: The Solution Framework
To solve these challenges, I ran co-creation workshops using a Service Design methodology (Double Diamond) combined with Agile practices. Out of 10 prioritized initiatives generated with the team, I deliberately chose to focus on people and career enablement rather than purely rigid processes.
The core interventions I structured focused on three main pillars:
- Refactoring the “Design Guild”: Re-architecting internal communities from passive presentation groups into active mentorship, career-tracking, and knowledge-sharing hubs.
- Operationalizing the Principles: Using our shared design values as explicit backing to negotiate research, discovery, and validation phases with clients and internal stakeholders.
- End-to-End Journey Alignment: Standardizing onboarding, structured feedback intervals, and internal references so that no designer is left operating in isolation on a client project.
Final Thoughts: Operating Design as a Craft
When design operates at scale in B2B tech organizations, methodology alone isn’t enough. Success comes down to creating an environment where designers can access their full potential, where non-designers respect the boundaries of the craft, and where internal growth is nurtured through continuous, structured community support.