Bridging Art, Design, and Technology with a Maker's Mindset

Tag: collaboration

From Figma to Replit: How AI Tools Are Dissolving the Agile Team
TL;DR: Tools like Replit make wireframes and handoffs obsolete, dissolving the traditional Agile team into AI-ready tasks and human responsibilities — and forcing us to reimagine collaboration around outcome-driven orchestrators.

For more than a decade, Figma symbolized the specialized silo of digital design. It gave product teams a shared canvas, but it also reinforced the structure of Agile squads: product managers, designers, developers, and QA each contributing their piece of the puzzle in sequence.

Now, with the rise of platforms like Replit, that division is starting to dissolve. In Replit, the prototype isn’t a static mockup waiting for translation into code. It’s live, executable, and deployable — design, build, and test happen in one environment.

This shift signals something much bigger than the replacement of a design tool. It points to the dissolution of the Agile team itself.

The Dissolution of Roles

In my book Agile Symbiosis, I argue that artificial intelligence acts as a universal solvent. It quietly breaks down the neat, stable containers we’ve built around jobs, tasks, and responsibilities.

The Agile team is one of those containers. For years, we assumed you needed four distinct roles to ship a digital product:
- A product manager to write user stories
- A designer to create wireframes
- A front-end developer to implement them
- A QA analyst to test the work
But with Replit, the wireframe itself becomes obsolete. Why sketch boxes in Figma only to rebuild them later? Today you can prompt Replit to generate functioning layouts and components directly in code. Mockups and handoffs — once necessary artifacts — are dissolving alongside the jobs that depended on them.

What remains are two elements: commoditized AI-ready tasks and enduring human responsibilities.

From Specialists to Orchestrators

This is where the Poly-Shaped Professional emerges. Instead of being narrowly defined by a single specialty, these new professionals orchestrate across domains with AI as their partner.

In Replit, a single builder can sketch a vision, generate interface components, integrate them into a working prototype, and refine it through rapid iteration. They’re not doing everything alone; they’re delegating the repeatable pieces to AI while focusing their energy on what remains uniquely human:
- Strategic creativity: envisioning the experience that should exist
- Deep user empathy: understanding the real problem to solve
- Complex systems thinking: aligning features with architecture and outcomes
- Ethical judgment: deciding when something is ready to release
The Agile team doesn’t vanish — it recrystallizes. Instead of four separate roles handing work off, you see new archetypes like the Customer Experience Architect, who owns outcomes rather than tasks.

Why Dissolution Matters

Dissolution isn’t destruction. It’s chemistry. By breaking compounds into elements, we can synthesize something stronger.

Replit is more than a productivity boost; it’s a catalyst that forces us to rethink collaboration itself. The old Agile rituals — sprint planning, backlog grooming, design handoffs — were built for a slower, siloed era. When one orchestrator can generate, test, and deploy in days, the handoffs become friction, not value.

If leaders cling to those structures, they’ll end up with what I call the “V12 engine bolted to wagon wheels”: hyper-productive individuals grinding against legacy processes that can’t keep up.

The Human Challenge

Of course, this transition isn’t just technical. It’s deeply personal.

Designers who once built their careers in Figma may feel their craft trivialized when AI skips their stage altogether. Developers may grieve the erosion of the skills that once defined them. This is the grief cycle of professional identity — denial, anger, bargaining, depression, and finally acceptance — playing out inside our teams.

If ignored, this grief metastasizes into division: empowered orchestrators on one side, legacy specialists on the other. That cultural fracture is far more dangerous than any tool disruption.

Re-Architecting Collaboration

The opportunity is to move deliberately. Dissolve the old roles, isolate the enduring human responsibilities, and synthesize new ones that better reflect today’s reality.

Replit replacing Figma is not just about tools. It’s about the architecture of work. The Agile team, as we knew it, is dissolving. What comes next is not smaller teams or fewer jobs, but a new kind of collaboration built on Agile Symbiosis: humans and AI partners working together to create outcomes that neither could achieve alone.

The solvent is already at work. The question is whether we’ll let it corrode our culture — or whether we’ll take up the role of chemists, deliberately shaping what recrystallizes in its wake.

The concepts introduced here are drawn from my forthcoming book, Agile Symbiosis: The Rise of the Poly-Shaped Professional in the Era of AI. In it, I explore how artificial intelligence is dissolving traditional roles and reshaping the way we work, collaborate, and create value.
September 13, 2025
6 Overlooked Keys to Making Agile Actually Work

Many organizations struggle with agile, not because the methodology is flawed, but because they overlook crucial elements that make it work. These six often-forgotten factors can transform your agile implementation from frustrating to flourishing. While there are many components to successful agile adoption, focusing on these essentials will improve product quality, reduce errors, and increase customer value. When your product makes your customers successful, you will be successful.

1. Drop the Methodology Mindset

The first step toward making agile work is abandoning the notion that methodology alone makes you agile. While frameworks provide valuable structure, management often embraces them simply because they feel familiar and controlled. Consider a team that perfectly follows Scrum ceremonies but struggles with actual collaboration – they’re following the methodology but missing the mindset.

Being agile is a state of mind where a team commits to working together, solving problems more efficiently, and delivering quality work faster. Success comes from combining both the framework and the mindset. One without the other leads to frustration and failed implementations.

2. Foster True Collaboration

Your team must be free to work collaboratively without the burden of company politics. When leadership actively shields a team from corporate distractions – like unnecessary meetings, competing priorities, or interdepartmental conflicts – it frees them to do their best work.

For example, a strong, agile leader might establish “no-meeting Wednesdays” or create clear boundaries around team priorities when other departments make conflicting requests. You’ve achieved true agile transformation if you can grow this protective, collaborative culture beyond individual teams. At its core, agile is collaboration codified.

3. Build Shared Ownership

Every team member should equally share responsibility for the product’s quality. This means becoming intimately familiar with the customer – understanding exactly who they are and why they need your product. When the team shares responsibility, they develop a sense of ownership that naturally elevates work quality.

Building a cohesive team where loyalty and trust prevail generates a powerful force that produces extraordinary results. This isn’t just idealistic thinking – elite military units use these exact principles to amplify the effectiveness of small tactical teams. It’s a proven approach to building high-performing teams.

4. Release Small, Release Often

Break work into small, deliverable elements that provide immediate customer value. Smaller batches are easier to test, faster to deliver, and simpler to manage because changes are incremental. Imagine confidently deploying new code every two weeks instead of dealing with massive, risky releases.

Larger features can still be deployed in small batches by implementing feature flags – switches that let you control feature visibility for different user groups. If you need more controlled rollouts, consider establishing a beta environment for key users. This allows you to learn, iterate, and improve before full deployment.

Many teams worry about release overhead, but modern CI/CD practices and automation can make frequent releases more efficient than large, infrequent deployments. The key is investing in your deployment pipeline upfront.

5. Free Yourself from Estimate Prison

Estimates are typically inaccurate guesses that set wrong expectations for both teams and stakeholders. Instead of spending energy on detailed estimations, focus on understanding and prioritizing customer needs. This keeps the team aligned with what matters most while maintaining a steady stream of improvements.

Commitments based on estimates will inevitably be broken, leading to finger-pointing that undermines collaboration. When you eliminate the pressure to provide precise estimates and rigid commitments, you free the team to do their best work and speed up delivery. The only commitment needed is staying focused on customer needs and goals.

6. Make Quality Everyone’s Job

Quality assurance isn’t a final checkpoint – it’s an integral part of every step in development. When the entire team has a holistic vision of the customer and product, you have more eyes on the work, and quality naturally improves. Teams who feel connected to their work catch defects before deployment.

Implement automated testing early in development and make it a shared responsibility. If you move testing away from the developers or treat it as a final step, you create opportunities for blame and catch issues too late. While user feedback is essential, it shouldn’t be your primary quality control. Move quality left in your process, not right.

The Real Key to Agile Success

Agile is fundamentally an attitude, not a methodology. It’s about working collaboratively toward shared goals that benefit your customers. Frameworks and methodologies are valuable tools that provide guidance, but they don’t magically improve how we work. Success comes from how we choose to work together, share responsibility, and maintain focus on what truly matters – delivering value to our customers.

Ready to improve your agile implementation? Start by examining how your team embodies these principles, not just how well they follow the methodology.

Image generated with the help of AI (ChatGPT & DALL·E).

August 17, 2022
Agile is Collaboration Codified
How Protected Innovation Spaces Drive True Agile Success

2000, I led digital product design for a revolutionary commercial banking portal. While most of the corporate world was still wrestling with waterfall methodologies and rigid processes, our team was already embracing what would soon be known as Agile principles – though we called it collaboration.

What made our approach unique wasn’t just the iterative process we used to build software. It was the environment that allowed innovation to flourish. We operated in a protected bubble within a giant bureaucratic organization, functioning more like a startup than a traditional corporate team.

Our workspace in San Francisco’s South of Market district reflected this philosophy. Beyond the superficial trappings of pool tables and bean bags, we had something far more valuable: permission to innovate. This permission came directly from senior leadership, who provided the funding and the political protection needed to operate differently.

The Power of True Collaboration

When the Agile Manifesto emerged in February 2001, it felt like validation rather than revelation. Our team had already discovered the power of working iteratively and collaboratively with multidisciplinary groups. We weren’t following a prescribed methodology – we were responding to real human needs:
- We brought together developers, designers, and business analysts every two weeks to review progress and adjust our course based on new insights.
- Our customer research team conducted ongoing interviews and usability tests, feeding insights directly to the development team.
- Instead of lengthy requirement documents, we used rapid prototyping and direct customer feedback to guide our decisions.
This wasn’t an accident. Our group’s leader had secured both executive support and substantial resources. They created what I now recognize as a crucial element for innovation: a protected space where teams could focus on building great products instead of navigating corporate politics.

The Challenge of Scale

In the decades since my time in that innovative bubble, I’ve observed the same company attempting various Agile transformations, each with different degrees of success. Some teams embraced the change naturally, while others resisted.

What separates success from failure isn’t the specific Agile framework chosen or the number of ceremonies performed. It’s the presence or absence of a truly collaborative environment. When teams focus on protecting territory, controlling processes, or avoiding blame, even the most carefully implemented Agile methodology will fail.

Creating Spaces for Innovation

The secret to successful Agile transformation isn’t in the methodologies – it’s in creating protected spaces where collaboration can thrive. Here’s what that looks like in practice:

Leadership Support
- Executive sponsors who actively shield teams from organizational politics
- Resources and time allocated for experimentation and learning
- Clear communication that failure is an acceptable part of innovation
Team Empowerment
- Authority to make decisions without multiple layers of approval
- Access to end users and stakeholders for direct feedback
- Freedom to adjust processes based on team needs
Cultural Safety
- Recognition for sharing ideas and raising concerns
- Celebration of learning from failures as much as successes
- Focus on outcomes rather than adherence to the process
Beyond the Methodology

You can’t expect to adopt a new, trendy process to fix deep-seated cultural problems or automatically make people more collaborative. True collaboration emerges when people feel safe taking risks, sharing responsibility, and claiming genuine ownership of their work.

The most successful Agile transformations I’ve witnessed share a common thread: they prioritize creating an environment where collaboration can flourish naturally. The specific framework – whether Scrum, Kanban or a hybrid approach – matters far less than the cultural foundation supporting it.

The Path Forward

For leaders looking to foster true agility in their organizations, the path forward is clear: focus first on creating protected spaces where teams can collaborate effectively. This means:
1. Actively removing political barriers that prevent open communication
2. Providing teams with the autonomy to make decisions
3. Demonstrating through actions, not just words, that innovation and experimentation are valued
Remember, Agile is simply collaboration codified. When you create an environment that naturally encourages collaboration, agility follows – not as a forced methodology but as the natural way of working together to create something extraordinary.

Image generated with the help of AI (ChatGPT & DALL·E).
August 16, 2022
Agile: A Path Forward, Not a Prescription
We’ve all encountered them – the Agile zealots who insist their way is the only way. While I’m passionate about effective work methods, I believe in being agile about Agile itself. Success can take many forms, but failure? That has endless variations.

When Process Becomes Prison

I once found myself in a project that perfectly exemplified dysfunction – a tangled mess of Agile and waterfall methodologies where team members drowned in anti-patterns. As the ship took on water, management’s solution was to demand more detailed reports about the sinking. Despite my attempts to suggest course corrections, leadership remained committed to their doomed trajectory. Their determination was admirable, but their direction was fatal.

The Foundation of Success

Through years of experience, I’ve observed that thriving projects consistently share these critical elements:
1. A balanced, multidisciplinary core team that brings diverse perspectives and skills
2. Collective ownership, where quality becomes everyone’s responsibility
3. Deep, shared understanding of customer needs and pain points
4. Psychological safety that encourages honest communication
5. Natural collaboration that emerges from the above elements
6. Leadership that enables rather than obstructs
Notice that none of these elements are tied to any specific methodology. They’re the lubricant that keeps the process machinery running smoothly. Without them, even the most perfectly designed process will eventually halt.

The Machine Metaphor

Think of your project as a machine: the process provides the gears, but these foundational elements are the oil. When things aren’t working, you have two options: redesign the machine or increase maintenance. The project I described earlier suffered from both poor design and insufficient maintenance—worse still, those who could help fix it were told to manually force the gears to turn instead.

Moving Forward

The key insight is simple: successful projects require empowered people working collaboratively to solve problems. Management’s role is to either clear obstacles or actively support the team – not to demand harder pushing of a broken system.

Large organizations can sustain dysfunction longer, but poor leadership creates rapid failure in smaller companies. If you find yourself in a broken system, you have options:
- Drive solutions from within your team (leveraging collective problem-solving capability)
- Partner with leadership to implement necessary changes
- Make personal choices that align with your professional values
Sometimes, despite our best efforts, organizations remain committed to problematic paths. In these cases, you must decide what’s right for your career and well-being.

Image generated with the help of AI (ChatGPT & DALL·E)
May 15, 2022