Design And Technology Collaboration That Actually Works
Most people in this space talk about design and tech as two separate departments that occasionally meet. Filippo Testa and Tamara Kalinics operated differently. Their collaborative approach, which I've studied closely through case studies and direct observation of their work, treats design and engineering as a single discipline from day one. I first encountered their methodology around 2018 when working on a product redesign project. We were hitting the standard wall where designers would deliver mockups and engineers would find half the interactions impossible to implement within reasonable timelines. Their approach completely sidesteps this by requiring technical feasibility to be part of the design conversation before any pixel gets placed on a screen. The core principle they developed is what I call concurrent constraint mapping. Rather than treating technical limitations as obstacles to work around after design decisions are made, both parties identify constraints simultaneously. Testa would sketch interaction flows while Kalinics would immediately flag component-level limitations. This back-and-forth typically takes 20-30% longer in the initial phases compared to traditional sequential workflows, but it eliminates the rework that usually follows.
One specific technique they used extensively was the interaction prototype loop. Instead of creating high-fidelity static designs, they would build working prototypes that demonstrated the actual behavior. These prototypes often ran on modified hardware setups because they needed to test edge cases that standard emulators couldn't replicate. I remember seeing them use a Raspberry Pi rig to test how certain haptic feedback patterns would translate across different device form factors. The setup looked rough, but it caught problems that no amount of Figma animation could reveal. Another counter-intuitive insight from their work is what I'd call deliberate constraint adoption. Most teams try to overcome limitations. Testa and Kalinics would sometimes choose to design around a specific technical constraint rather than push against it. For example, when working on a mobile interface project, they noticed that thumb reachability was a genuine hardware limitation on larger screens. Instead of designing for all screen positions equally, they structured the entire interaction model around a single-thumb operating zone. This actually improved the experience because every element had a clear, discoverable placement. The collaboration also involved what I think of as cross-disciplinary whiteboarding sessions. These weren't casual brainstorming meetings. They were highly structured sessions where both parties had to explain their reasoning in real-time. If Testa proposed a visual solution, Kalinics had to immediately articulate the implementation path and vice versa. This created a shared mental model that persists throughout the project lifecycle. Team members who weren't part of these sessions often struggled to understand why certain decisions were made, which was a documented limitation of the approach.
I encountered a specific problem when trying to adapt their method for our team. We had senior engineers who were resistant to the concurrent workflow because they felt it slowed down their individual contribution. The workaround I found was to split the sessions into two phases: initial constraint mapping followed by independent execution periods. This preserved the collaborative advantage while giving engineers the autonomy they needed. It wasn't a perfect reproduction of Testa and Kalinics' process, but it got us 80% of the benefit. Their work also emphasized hardware-software co-design. This was particularly evident in projects where the physical device shape directly influenced the software interface. Rather than designing software for an existing hardware spec, they would iterate on both simultaneously. I've seen wireframe sketches that included notes about button depth, material feel, and thermal constraints alongside visual layout decisions. This level of integration is rare and requires a specific type of collaborative environment that most organizations don't naturally support. One thing worth noting about their approach is that it doesn't scale well to large teams. The methodology works best with groups of 4-8 people who have established trust and shared context. When I've tried to apply their techniques to teams of 15 or more, the coordination overhead tends to overwhelm the benefits. In those situations, a modified version focusing on just the constraint mapping aspect works better than attempting the full approach.
Get the Full Details
For anyone looking to implement something similar, start with a single feature or module rather than trying to transform an entire product line. The learning curve is steeper than traditional methods, and early failures in a low-stakes environment provide better training value than early failures in your flagship product. Budget for an additional 2-3 weeks in your timeline during the initial adoption period. The return on investment becomes clear after roughly 3-4 project cycles.
Practical Application Notes
The tools themselves matter less than the process. Testa and Kalinics have used everything from paper sketchbooks to sophisticated 3D modeling software depending on the project phase. What remains constant is the requirement that both design and technical thinking happen in the same room, in real-time, with immediate feedback loops. Remote collaboration can approximate this with video calls and shared digital whiteboards, but the quality of interaction tends to degrade compared to in-person sessions. I'd recommend examining their published case studies and any available footage of their working sessions. The nuances of how they handled disagreement, pivoted when constraints changed, and maintained creative momentum despite technical obstacles are visible in practice but harder to extract from written descriptions alone.
