Architect’s blog

Mugunthan Ravichandran Solution Architect of fter.io

10.6.2026 – The impact looks very different from each seat

In my previous post I talked about the AI-powered development ecosystem we are building at fter.io. Today I want to share what it actually changes depending on where you sit in the team.

Because the impact looks very different from each seat.

For the Product Owner – the biggest shift is that requirements no longer get lost in translation. When a PO writes a ticket, that context flows directly into the AI workflow. Claude has the requirement when generating code. Fewer misunderstandings. Fewer cycles back to clarify. And because the system accumulates context over time, product knowledge stops living only in people’s heads.

For the Product Designer – the gap between what you designed and what gets built gets significantly smaller. We connected our design system directly to our code repository. Claude Design identifies components that exist in design but are missing in code and creates them. Implemented. Aligned to our patterns. The design system becomes a living source of truth, not a Figma file that developers interpret differently every time.

For the Developer – context is already there when you pick up a ticket. Generated code fits how your team builds aligned to your design system, your architecture standards, your conventions. Reviews are structured and not blocked by who happens to be available. And tests are part of the build, not an afterthought added under pressure at the end of a sprint.

For the QA Engineer- quality stops being a phase and starts being a property of the system. Automated tests are generated during development, not requested after it. Edge cases that are easy to miss under time pressure get caught early. By the time something reaches a tester, it has already passed through multiple AI-assisted quality layers. The role does not disappear it gets more interesting.

The common thread across all four? AI does not replace the judgment that each role brings. It removes the friction that gets in the way of doing that job well.

One architecture. Four very different impacts.

What’s on your mind regarding all this?