The machines got smarter. So did the human work.

There were no mockups. No component libraries. No color tokens. No screens to stare at in a design review while someone asks if the font could be slightly bigger.

Just a different kind of question than I was used to asking:

Who is E.L.L.A., and what does this actually do?

I am part of the Robots & Pencils team working with FleetHub.AI to shape E.L.L.A.’s experience, and I quickly realized we weren’t designing another interface. We were designing how an intelligent system should behave around a person.

Inside the Design of E.L.L.A., FleetHub.AI’s Voice Co-Pilot for Truck Drivers

FleetHub.AI is building a connected technology stack for commercial trucking fleets. At the center of that vision is E.L.L.A., a voice-first AI co-pilot designed to live in the cab alongside truck drivers, not as another app competing for attention, but as an intelligent layer connecting the systems already at work around them. Underneath, E.L.L.A. runs on Amazon Nova 2 Sonic for real-time voice and Amazon Bedrock for reasoning, with AWS Lambda, Amazon API Gateway, and Amazon DynamoDB handling everything in between.

We weren’t designing another interface for a driver to look at. We were designing how an intelligent system should listen, interpret, respond, and know when to stay out of the way.

E.L.L.A. had to work across a complicated technology environment while making the experience feel simple for the person behind the wheel. A co-pilot, not another screen. Something that needed to understand the difference between a driver who needed a heads-up about road conditions and a driver who needed silence. Something that had to know when to surface a delivery conflict, when to help, when to act, and when to simply let the road go by.

Eyes on the road. Hands on the wheel.

In this environment, every interaction that asks a driver to look away carries a cost. Visual design wasn’t irrelevant, but it couldn’t be the primary way E.L.L.A. communicated. The experience had to work without requiring the driver’s eyes.

Designing a Voice AI Persona for Trucking Means Asking Human Questions, Not UX Questions

The difference this time was what I was actually designing.

Not an experience built around a person. A person.

Not a screen a driver would glance at, but a presence a driver would talk to.

That meant designing a character: a voice, a sensibility, a set of behaviors, and a sense of when to speak and when to pause. It was one of the most human design problems I’d worked on, and it had almost nothing to do with visual design.

What would I want to hear if I’d been driving for six hours? What information would feel helpful at mile three and overwhelming at mile forty? If I was running late and stressed, would I want a conversation, or would I want E.L.L.A. to handle it quietly and tell me when it was done?

At what point does a helpful nudge become noise?

And once you answer that, what’s the next layer?

What if the driver just got off a difficult call? What if traffic is about to add forty minutes to an already-long day? What if something changes in the delivery workflow while the driver is moving?

These weren’t UX questions in the way I’d always framed them.

They were human questions.

The more I worked on E.L.L.A., the less I thought of her as a voice interface and the more I realized we were designing how she should behave — how she should understand context, make judgments, respond to a person, and know when to speak or stay quiet.

That distinction mattered.

A traditional interface gives someone a place to go and things to interact with. E.L.L.A. had to do more of the work. Her behavior had to account for what was happening around the driver, determine what mattered, and decide how — or whether — to bring it into the conversation.

That meant we weren’t just designing what E.L.L.A. would say.

We were designing the conditions under which she should speak at all.

Answering those questions required me to sit in the driver’s seat, not literally, but fully. To model a person, not just a user flow.

That project changed something in how I see our work.

E.L.L.A. made one thing impossible to ignore: when you strip away the screen, design doesn’t disappear. It moves somewhere else.

It moves into judgment.

Why Voice AI Design for Trucking Demands Human Judgment

We talk a lot right now about how AI is transforming design. The tools are faster. The cycles are compressed. What used to take three weeks of exploration can surface in three hours. I won’t argue with any of that.

But I think we’re sometimes tempted to let the speed of the tools define the conversation. To make the story about efficiency. About throughput. About how many design variations we can generate before lunch.

And I’d push back on that, not because the speed isn’t real, but because it’s not the point.

E.L.L.A. didn’t need more variations. She needed judgment.

She needed someone to think carefully about what a human being, inside a specific context, on a specific kind of day, would actually find useful.

No tool was going to figure that out.

That thinking had to come from somewhere, from someone willing to put themselves in those shoes and stay there long enough to feel the weight of the question.

And in trucking, that context matters.

A driver isn’t sitting at a desk waiting for information. They’re managing a long day on the road, navigating traffic, schedules, deliveries, communications, compliance requirements, and everything else that comes with keeping a truck moving.

The challenge isn’t necessarily a lack of information.

It’s too much of it, arriving through too many systems, at too many moments.

Good voice AI has to make that complexity feel simpler, not add another layer of noise.

That’s where judgment becomes part of the design.

When the Interface Becomes Behavior

Here’s what I keep coming back to.

With traditional digital products, we spend a lot of time designing what people see, where they tap, what happens next, and how information is organized on a screen.

With conversational and agentic AI, some of that work moves upstream.

We’re designing what the system knows. What it notices. What it prioritizes. What it does on someone’s behalf. What it says. How it says it. And, perhaps most importantly, what it chooses not to say.

The design artifact becomes behavior, not interface.

For E.L.L.A., that meant thinking about timing as carefully as content.

The right information at the wrong moment is still the wrong experience.

A useful notification can become an interruption. A well-intentioned prompt can become noise. A perfectly designed response can still be wrong if it arrives when the driver doesn’t need it.

The intelligence isn’t just in having the answer.

It’s in knowing when the answer matters.

The Design Work That Doesn’t Change

Here’s what I keep landing on:

The canvas has changed.

Interfaces are becoming ambient, conversational, and layered. With E.L.L.A., we weren’t just designing a screen or even a voice. We were designing an intelligent layer between a person and the systems surrounding them — one that had to account for what mattered, what could wait, and what didn’t need to be said at all.

We’re no longer just designing what people see.

We’re designing the conditions under which a system decides how to meet them.

That’s a bigger, stranger, more interesting problem than we’ve had before.

But the core of the work?

Unchanged.

We are still, fundamentally, in the business of understanding people well enough to know what they need before they’ve figured out how to ask for it.

That has always been the job.

Screens were just one era’s answer to how you meet a person where they are.

The tools get faster. The outputs get more sophisticated. The systems get more capable.

And every time the canvas shifts — from web to mobile, from mobile to voice, from voice to whatever comes next — the designers who do the best work are the ones who go back to the same question.

Not what can I build? What does this person actually need?

E.L.L.A. made that question feel especially real because the person at the center of the experience can’t always look at what we’ve built.

So, we had to design for everything else.

For attention. For timing. For trust. For context.

For knowing when to speak.

And when to let the road go by.

That’s what good design does.

It always has.

Learn more about Robots & Pencils’ solutions for the transportation industry.

About the Author

Brad Istnick is Principal Experience Creative at Robots & Pencils, where he helps shape how intelligent systems speak, listen, and decide — turning complex AI behavior into interactions that feel less like software and more like presence.

Key Takeaways

• Voice AI changes the design problem. When drivers can’t rely on a screen, designers have to think beyond visual hierarchy and into behavior, timing, and conversational judgment.
• E.L.L.A. is designed as more than a voice interface. She acts as an intelligent layer between the driver and the increasingly complex technology environment inside the cab.
• Good AI knows when not to speak. The right information at the wrong moment can still create a poor experience.
• Designing AI means designing behavior. What a system notices, prioritizes, says, does, and chooses not to do are all part of the experience.
• Human judgment remains essential. Faster AI tools can generate possibilities, but they don’t replace the human work of understanding what someone actually needs in a specific context.
• The canvas is changing, but the job isn’t. Whether the interface is a screen, a voice, or something else entirely, good design starts with understanding the person on the other side.

FAQs

What is voice AI for truck drivers?

Voice AI for truck drivers is AI technology that allows drivers to interact with information and fleet systems through natural conversation rather than relying primarily on screens, tapping, or manual navigation. The goal is to make information and assistance available while minimizing unnecessary visual and manual interaction with technology.

How does E.L.L.A. work as a voice AI co-pilot for commercial fleets?

E.L.L.A. is FleetHub.AI’s voice-first AI co-pilot, designed specifically for the commercial trucking environment. Rather than functioning as another standalone application, E.L.L.A. is designed to work as an intelligent layer across the systems and information surrounding the driver, helping determine what matters, when it matters, and how it should be communicated.

What is E.L.L.A. built on?

E.L.L.A. runs on Amazon Nova 2 Sonic for real-time voice and Amazon Bedrock, using Claude 3.5 Haiku for reasoning. AWS Lambda, Amazon API Gateway, and Amazon DynamoDB handle everything underneath the conversation.

How is E.L.L.A. different from a traditional voice assistant?

E.L.L.A. isn’t designed as a general-purpose voice assistant. She’s purpose-built for commercial trucking and the specific operational context of a professional driver. Her value comes not simply from answering questions, but from understanding the environment in which the driver is working and helping turn complex fleet information into timely, conversational assistance.

How is designing voice AI different from traditional UX design?

Designing voice AI moves much of the design work beyond screens and visual flows. Designers have to define a system’s voice, personality, behaviors, timing, decision-making, and rules for when it should speak and when it shouldn’t. The design artifact becomes behavior, not just interface.

How can voice AI reduce driver distraction?

Voice AI can reduce the need for drivers to physically interact with multiple applications while driving by making information and certain interactions available conversationally. The goal isn’t to eliminate every visual interface, but to reduce unnecessary moments when a driver needs to look away from the road to interact with technology.

What makes a good voice AI experience for truck drivers?

Context-awareness and judgment. A good voice AI understands that the same information can have very different value depending on what the driver is doing, what has already happened, and what requires attention right now. It earns trust by getting the timing right — not simply by having the right answer.

The post Designing Voice AI for Truck Drivers: The Human Questions Behind E.L.L.A.  appeared first on Robots & Pencils.

Twenty years ago a parent told their kid not to major in art. Ten years ago they said it about English. Five years ago the script tightened to anything that didn’t end in -ology or -engineering. STEM was the moat. STEM was the parachute. STEM was the answer to every dinner-table question your kid was too polite to ask out loud. 

You know how this ends. 

I’ve been watching it end in slow motion for eighteen months. The CS grads I talk to are anxious in a way the comp lit grads aren’t. Not because the comp lit grads have it figured out. They don’t. Nobody does. But they were never promised the floor wouldn’t move. The CS grads were told it was bedrock. Then somebody started writing code at the speed of thought, and the bedrock turned out to be a Jenga tower with a six-week release cycle. 

The irony is thick enough to spread on toast. We trained a generation to speak the language of machines. The machines turned around and learned the language of people. If a screenwriter pitched that arc, the room would tell them to dial it back. 

The company whose name explained everything

I want to tell you a story about a company I ran, because I think it explains what’s actually happening, and what’s coming for the people who were paying attention. 

In 2014, I brought a Canadian agency called Robots & Pencils down to the States. I was CEO of the US operation. We grew thirty-four hundred percent in eighteen months, finished the year as the 35th fastest-growing tech company in the country, and most of the press I gave at the time was about the numbers. The numbers weren’t the story. The name was. 

Robots & Pencils. The name was lifted, more or less, from C.P. Snow’s 1959 lecture on the Two Cultures. Snow’s argument that the sciences and the humanities had drifted into separate languages that could no longer talk to each other, and that the gap between them was the central problem of modern life. He wrote it about Cambridge dining halls. We built it as an agency. 

The robots were the developers. People who could build the thing. The pencils were the designers. People who could see the thing before it existed. Two trades, two trainings, two languages, two halves of any product worth shipping. We had robots. We had pencils. We were good at both. 

And the founder, who was (ironically, beautifully, to his own ongoing amusement) robot #1, was the most insistent voice in the building that good products are always visioned pencils first. You can’t bolt art on at the end. Try it and the seams show forever. The most technical man in the room kept telling the room to start with the drawing. 

Two people who were already the bridge

He didn’t found the company alone. His wife was the pencil to his robot, a brilliant artist, an interior designer with the eye that finds the wrong wall and tells you why, an accountant sharp enough to serve as the company’s CFO. He was the technical man with a love of art he couldn’t fake. She was the artist with the operational backbone most companies wish they could hire. Each of them stretched toward the center. Each of them was already half ampersand before the company had a name. 

That’s why it worked. The two people at the top of the org chart were the bridge they were asking the rest of us to build. You felt it the second you walked in. It pulled in robots who suspected they were also a little bit pencil, pencils who knew they were also a little bit robot, and the people who’d never picked a side at all. The brand wasn’t a logo. The brand was the marriage. 

But the ampersand was the entire reason the company existed. 

The rarest person in any room

You know who I mean. The dev who notices the kerning. The designer who reads the API docs because she actually wants to know what’s possible. The one who drops #picky into a Slack design review without apologizing for it, because they know the small thing is the whole thing. The person who can sit between two rooms that don’t speak each other’s language and translate. Not the words. The intent. They were rare. We’d interview a hundred people and find one. They commanded a premium because the value of a translator scales with the distance between the parties, and the distance between an engineer and a designer in most companies is bigger than the distance between Calgary and the moon. 

The ampersand people weren’t better at either trade. They were the only ones in the room who saw both trades as the same problem from different chairs. They were almost mythological. We named the company after them. 

What AI actually does for the bridge person

Here is what I didn’t see coming, even though I should have. AI doesn’t pick a side. It never had to. It doesn’t just close the gap between the dev and the designer. It closes the gap inside the bridge person, the small and humiliating gap between what they could always see and what they could actually produce. The designer who knew exactly how the API should work but couldn’t write the call. She can write the call now. The dev who saw the right pixel grid but couldn’t move pixels. He can move pixels now. The ampersand always saw both ends of the bridge. Now they can walk it. If Jobs called the computer a bicycle for the mind, AI just strapped rocket engines to the sides. 

You want proof? A 23-year-old amateur mathematician named Liam Price, no PhD, no faculty appointment, no research lab, used ChatGPT to solve an open problem that had been sitting on the shelf for sixty years. Erdős Problem #1196, from primitive set theory. Sixty years. The kind of problem that gets named after the person who posed it because nobody alive could finish it. Price finished it. And then Terence Tao, the Fields Medalist, the person most mathematicians would rank as the best living mind in the discipline, verified the proof and co-authored the resulting paper. A 23-year-old with curiosity and a chatbot sat down at the same table as the greatest mathematician of his generation. Not because AI solved the problem for him. Because AI let him hold the conversation long enough to solve it himself. That’s the ampersand. That’s curiosity with tooling that doesn’t punish you for not having the right letters after your name. 

The bridge people are about to multiply. Not because the trait gets more common. That takes generations, and curiosity in two directions has never been on any roadmap I’ve ever seen. But the trait finally has tooling that doesn’t punish it for refusing to specialize. For thirty years we paid the ampersand person less because they weren’t “really” a developer or “really” a designer. We tolerated them because they made the meetings work. They are about to inherit the building. 

And the lesson runs wider than design and code, because the ampersand was never really about design and code. The ampersand is about being curious in two directions at once. It’s about being the kind of person who refuses to pick a side because they can’t stand to leave the other side ignorant. That’s not a job description. That’s a humanities education. 

Read carefully. Argue clearly. Hold a contradiction without flinching. Care about the answer even when nobody’s grading you. Do the hard thing quietly. Take care of the person next to you before you take care of yourself. Carry two trades at once and a third in reserve. Say what you mean and mean what you say. It doesn’t sound like much. It also doesn’t fit in a job code, which is why we’ve been quietly defunding it for forty years. It didn’t return on a single-year horizon, and the only people who tried to defend it sounded like they were defending themselves. 

I’ll tell you where I learned all of it, because it wasn’t school. It was my parents and the people they surrounded us with. A father who came up through the Green Berets and ran a house on the principle that you say what you mean and you mean what you say. A mother and a community who treated curiosity as a chore you didn’t get to skip. Nobody handed me a syllabus on holding a contradiction. I watched the adults around me do it at the dinner table. I graduated into the internet in 1985 and was running an ISP a decade later. That sharpened the tools. The tools came from home. 

That’s the part the system can’t replicate and won’t admit. The ampersand is mostly raised, not taught. The people who saw this moment coming were mostly the ones we wouldn’t fund. And the ones who can step into it now were mostly raised by people who didn’t need a funding line to know it mattered. 

The skill with a 25-year half-life

Framework knowledge has a half-life of about two and a half years. That’s IBM’s number for specialist technical skills, and it tracks with what the National Academy of Engineering has been saying for twenty years. By contrast, the half-life of a humanities education runs closer to twenty-five. The argument structure Aristotle taught is still the argument structure that wins. The people who can build and fix the machine will be needed for as long as there’s a machine. The play isn’t picking a side. It’s picking one discipline that ages well and one that compounds fast, and refusing to let either atrophy. 

Walk into a room where the pencils and the robots are really cooking and you can feel it through the floor. The designers sketch faster than the engineers can build. The engineers build faster than the designers can sketch. The ampersand is at the whiteboard turning the sketch into a system and the system into a sketch, and everybody in the room is operating one cognitive notch above where they could operate alone. That hum used to be the rarest sound in tech. We’re about to hear it everywhere. In classrooms, in clinics, in non-profits, in offices that have been quietly dying for a decade because the bridge person never showed up. 

Don’t mistake this for triumphalism. The reversal doesn’t make the humanities grad rich and the CS grad poor. It rearranges who has leverage, which is a different and harder problem. The CS grads who pair their craft with the human stuff, curiosity in two directions, care for the person on the other side of the screen, are going to be fine. The humanities grads who learned to type sentences but never learned to sit with a real problem until it broke? They’re going to wash out the same as anyone. The credential never saved anybody. The skill underneath the credential is the only thing that matters now. 

What’s coming is a world where you need both hands. The robot hand and the pencil hand. The technical and the human. The thing the machine can amplify and the thing the machine cannot replace. People who learned only one are about to find themselves doing half a job. People who learned both, the ampersands, the bridge people, the curious-in-two-directions people, are about to find the assignment finally suits them. 

The career advice parents need to hear in 2026

I’ll say something with an edge, because I have watched too many parents push too many kids in the wrong direction and I am out of polite ways to put it. Stop telling your daughter to pick something “practical.” There is nothing practical about training her for a job description that will be rewritten before she graduates. Tell her to chase the thing she is actually curious about, and tell her to learn the tools that scale curiosity. That is the practical answer in 2026. Everything else is nostalgia for a stability that was always a marketing slogan. 

And tell her to find the room. Find a university, a community, a circle that’s already wired for curiosity in two directions. Humanities and sciences sitting at the same table, AI amplifying both, and credentials that still translate into workforce currency on the other side. Skills, capabilities, and a degree. Not one or the other. Humble plug, because it would be dishonest not to say it: that’s exactly what we’re building at Maryville. An achievement architecture for all of them. Robots, ampersands, and pencils. AI amplifying each one’s curiosity and capabilities. We’re about to show, not tell, what that means. Stay tuned. 

The ampersand was always the symbol of the company because it was the symbol of the work. Two trades, one person, one connector character holding the whole sentence together. It was never decoration. It was the structure. 

The robots are getting better. The pencils are getting better. But the people who can hold both, who can be technical without losing their humanity, who can be human without abandoning the craft, those people are about to inherit the moment. The ones we underpaid for thirty years because we couldn’t fit them in a column. 

Strive to be a little ampersand. Not just the robot. Not just the pencil. The character in the middle that connects them. 

That’s the job now. And it’s the abstract of every job that comes after it. 

The team Phil wrote about? That’s us. Robots & Pencils has been building at the intersection of technical and human since day one. Request an AI briefing and see what that means for your organization.

About Phil Komarny

Phil Komarny, an award-winning executive, national thought leader, and Chief Future/AI Officer at Maryville University. He led Robots & Pencils as CEO in 2014 and 2015. It’s clear he never stopped thinking about what our name meant. Read more articles by Phil.

Key Takeaways

1. The “ampersand person” is someone curious in two directions at once — technical and human — and they have always been the most valuable person in the room.
2. AI doesn’t replace the bridge person. It closes the gap between what they could always see and what they could actually produce.
3. Framework knowledge has a half-life of roughly two and a half years. The skills underneath a humanities education run closer to twenty-five.
4. For thirty years we underpaid the generalist because they didn’t fit a job code. That’s about to change.
5. The practical career move in 2026 is pairing one discipline that ages well with one that compounds fast — and refusing to let either atrophy.

FAQ

What is the ampersand person? Someone who refuses to specialize in just one direction. They can sit between two rooms that don’t speak each other’s language and translate not the words, but the intent.

Why is the Robots & Pencils name significant? The name draws on C.P. Snow’s 1959 Two Cultures lecture — the idea that the sciences and humanities had drifted into separate languages. Robots represented the builders. Pencils represented the visionaries. The ampersand between them was always the point.

How does AI change things for generalists? AI closes the gap between what bridge people could always see and what they could actually produce. The designer who knew how the API should work can now write the call. The developer who saw the right pixel grid can now move pixels.

Is a humanities education still worth it? According to Phil Komarny, yes — more than ever. The argument structure Aristotle taught still wins. The credential doesn’t save anyone, but the skill underneath it compounds in a way technical specialization alone no longer does.

What should parents tell their kids about careers in an AI world? Stop pushing “something practical” defined by yesterday’s job market. Tell them to chase what they’re genuinely curious about and learn the tools that scale curiosity. That is the practical answer in 2026.

The post The Ampersand: Generalists in the AI Era appeared first on Robots & Pencils.

What surprised me most was not curiosity about artificial intelligence. 

It was fear. 

Almost everywhere I go, I hear the same concern from students. They worry that artificial intelligence will remove entry-level design jobs before they even have a chance to begin their careers. For many of them, AI represents something that replaces designers rather than something that enhances what designers can do. 

Rethinking What Professional Experience Means in Design 

The concern is understandable. When you are about to graduate and enter the workforce, the last thing you want to hear is that the profession itself may be changing faster than expected. 

But after spending many years reviewing portfolios and hiring designers, I have started to see the situation a little differently. 

Students may be worrying about the wrong thing. 

For a long time, professional experience in design meant something very specific. It meant understanding the tools, the workflows, and the production processes that turn ideas into finished work. Designers spent years refining their craft while also learning how the industry operates. With enough time, that accumulated knowledge created a real advantage. 

A designer with fifteen years of experience typically knew how to do things faster, more efficiently, and often with a higher level of quality than someone just entering the field. 

How Artificial Intelligence is Changing Design’s Professional Experience Curve 

AI is not simply another tool added to the designer’s toolkit. In many cases, it is reshaping the workflow itself. Tasks that once required deep technical knowledge or years of production experience can now be explored, tested, and iterated much more quickly with modern AI tools for designers. 

What this means is that the distance between a junior designer and a senior designer is starting to shift. 

A young designer who grows up alongside AI-assisted design tools can move through experimentation, prototyping, and production at a pace that used to take many years of experience to achieve. Instead of slowly accumulating knowledge about how to produce work, they can focus earlier on exploring ideas and refining their quality. 

In other words, the professional experience curve for designers is compressing. 

A Pattern Creative Industries Have Seen Before 

We have seen something similar happen before in other creative industries. 

For decades, producing professional music required access to expensive studios, specialized equipment, and engineers who understood complex recording systems. Experience in the music industry meant knowing how to navigate that entire infrastructure. 

Then digital production tools changed everything. Software like Logic and Pro Tools turned laptops into recording studios. Experimentation became cheaper, faster, and far more accessible. 

One of the most well-known examples is Billie Eilish, who recorded her early music with her brother in a bedroom studio using digital production tools. They did not come up through traditional studio systems. They grew up inside the new tools. 

The technology did not replace musical craft. If anything, it made the importance of taste, storytelling, and artistic identity even more obvious. But it did compress the experience curve. Young creators who understood the new tools could suddenly compete with artists who had spent decades working inside the old system. 

Something very similar appears to be happening in design. 

Why Craft and Taste Still Matter 

This does not mean that craft disappears. In fact, craft may become even more important. 

Artificial intelligence can accelerate exploration and production, but it does not replace taste, judgment, or the ability to understand why a design solution works. When reviewing portfolios, those qualities are still what stand out the most. The designers who succeed are the ones who demonstrate thoughtful decisions, strong visual communication, and a clear point of view. 

But the role of experience is evolving. 

The Rise of AI-Native Designers 

For decades, experience meant knowing the established systems better than someone else. Now experience increasingly includes the ability to adapt quickly, integrate new tools into the creative process, and rethink how work gets done. 

Students entering the field today are learning these tools, and at the same time, they are learning design itself. In many ways they are becoming AI-native designers, a generation of creatives who develop design craft alongside artificial intelligence and AI-assisted design workflows. 

This may create something the design industry has rarely seen before. 

For the first time, the youngest designers entering the profession may also be the most technologically fluent. 

That changes the competitive landscape. 

A New Advantage for the Next Generation of Designers 

A talented young designer who understands both craft and emerging technologies may be able to produce work that rivals someone who has spent far longer in the field. The years of experience that once created a clear advantage are no longer the only factor in shaping capability. 

This is why the conversation around AI in design needs to shift. 

Instead of asking whether AI will eliminate entry-level roles, we may need to ask a different question. How is the definition of professional experience in design changing? 

Because if experience is no longer measured only by time spent in the industry, but also by how effectively designers adapt to new tools and new workflows, then the playing field begins to level. 

And when that happens, the advantage may not belong to the people who have simply been around the longest. 

It may belong to the designers who are learning the fastest. 

For students entering the profession today, that should be encouraging rather than frightening. They are learning design and at the same time the tools and processes are evolving. They have the opportunity to build their craft while also developing fluency in technologies that many established professionals are still figuring out. 

Moments like this do not happen often in a profession. But when they do, they tend to redefine who has the advantage. 

Right now, the next generation of designers may be closer to that advantage than they realize. 

If you are a designer who is curious about new tools, interested in how artificial intelligence is changing creative work, and excited about pushing the craft forward, we would love to hear from you.  Robots & Pencils is always looking for designers who combine strong visual thinking with a willingness to explore new technologies and new workflows. View open design roles. 

Key Takeaways 

• Artificial intelligence is changing how designers gain professional experience rather than replacing designers. 

• AI tools for designers allow faster experimentation, prototyping, and production. 

• The gap between junior and senior designers may shrink as AI compresses the professional experience curve. 

• Craft, taste, and visual judgment remain essential design skills. 

• Students entering the field today may become AI-native designers, combining design craft with emerging technologies. 

FAQs 

Will AI replace designers? 

Artificial intelligence is unlikely to replace designers. AI tools can accelerate experimentation, ideation, and production, but they do not replace creative judgment, storytelling, or visual taste. 

Should design students be worried about AI? 

Many design students worry that artificial intelligence will remove entry-level jobs. In reality, AI is changing how designers develop experience. Students who learn AI assisted design tools early may gain a competitive advantage. 

What are AI tools for designers? 

AI tools for designers are systems that help generate visual ideas, explore design variations, automate production tasks, and accelerate creative workflows using machine learning models. 

What is an AI-native designer? 

An AI native designer is someone who learns design craft and at the same time they learn artificial intelligence tools. Instead of adopting AI later in their career, they grow up designing alongside AI assisted workflows. 

How is AI changing design careers? 

Artificial intelligence is compressing the experience curve in design. Designers can experiment, prototype, and refine ideas much faster than traditional workflows allowed. 

The post Should Design Students Fear AI? appeared first on Robots & Pencils.

There is a simple truth in basketball: when someone claims they can dunk, you do not want their biography. You want to see them take off, rise above the rim, and throw it down. Until the ball goes through the hoop, everything else is just pregame chatter. 

Traditional business pitches are no different. Slide after slide explaining talent, process, and commitment to excellence. Everyone insists they are fast, strategic, and powered by artificial intelligence. It all blends together. 

And just as in basketball, none of it matters until you see the dunk. 

Why Enterprise AI Partner Evaluation Has Changed 

I have spent the last year watching something shift in how enterprise buyers evaluate technology partners. The change is not subtle. AI collapsed the timeline for what is possible. Engineers use artificial intelligence to automate repetitive tasks, reveal gaps, and support rapid iteration. User experience teams model real behavior and refine interactions in a fraction of the usual time. Designers explore and adapt visual directions quickly while matching a client’s brand and needs. At the strategy level, artificial intelligence helps teams explore concepts, identify edge cases, and clarify problems before anyone designs anything or writes code. 

Teams can now build first versions far earlier than they once could. It is now possible to walk into a meeting with something real, rather than something hypothetical. 

Traditional Evaluation Arrives Too Late  

Yet enterprise evaluation still moves as if early builds take months. Teams can create quickly, but organizations are asked to decide slowly. Forrester’s 2024 Buyers’ Journey Survey reveals the scale of this shift: 92% of B2B buyers now start with at least one vendor in mind, and 41% have already selected their preferred vendor before formal evaluation even begins. Traditional vendor selection leans on slides that outline intent, case studies that point backward, and demos that highlight features. These keep judgment at arm’s length and often arrive too late to matter. 

An early milestone changes that dynamic. A deck explains. A first version proves. 

What Functional Products Reveal About AI Vendors 

A healthcare technology company came to us through a partner referral. They needed to modernize their pharmacy network’s web presence, which included hundreds of independent pharmacy websites, each with unique branding and content, all needing migration into a modern, SEO-optimized content management system. They had already sat through multiple vendor presentations that week. Each promised speed, AI capabilities, and transformation. 

At Robots & Pencils, we stopped presenting what we could do and started showing what we already built. 

Building the Functional Product in 10 Days 

Our team had a week and a half. Our engineers used AI agents to automate content scraping and migration. Our UX team modeled user flows and tested assumptions in days instead of weeks. Our designers explored visual directions that preserved each pharmacy’s brand identity while modernizing the experience. Our strategy team identified edge cases and clarified requirements before a single line of production code was written. 

We walked into the meeting with a functional product. 

The Client Demo: Testing Real Data in Real Time 

The client entered one of their pharmacy’s existing URLs into our interface. They selected brand colors. They watched our AI agents scrape content, preserve branding structure, and generate a modern, mobile-responsive website in real time. Within minutes, they were clicking through an actual functioning site built on a production-grade CMS with an administrative backend. This was not a mockup or a demo, but a working system processing their real data. 

The entire conversation shifted. They immediately started testing edge cases. What about mobile responsiveness? We showed them the mobile view that we had already built based on pre-meeting feedback. What about the administrative interface? We walked them through the CMS backend where content could be updated. They stopped asking, “Can you do this?” and started asking “What else can we build together?” and “How quickly can we expand this?” 

After the meeting, their feedback was direct: “I appreciate the way you guys approached us. Going through the demo, it wasn’t just this nebulous idea anymore. It was impressive from a build standpoint and from an administration standpoint.” 

Why Early Functional Products Prevent Partnership Failures 

When clients see a working product, even in its earliest form, they lean forward. They explore. They ask questions. They do not want to return to a deck once they have interacted with actual software. And this is precisely why the approach works. 

Most enterprise partnerships that fail do not fail because of weak engineering or design. They fail because teams hold different pictures of the same future, and those differences stay hidden until it is too late to course correct easily. A shared early version fixes that. Everyone reacts to the same thing. Misalignments surface when stakes are low. You learn how a partner listens, how they adjust, and how you work through ambiguity together. No deck presentation can show these things. 

How Early Functional Delivery Transforms Vendor Selection 

The Baseline Iteration Before Contract Signing 

At Robots & Pencils, we think of this functional product as more than a prototype. It is the baseline iteration delivered before contract signing. It shapes how the partnership forms. The client comes into the work from the start. Their data, ideas, and context shape what gets built. 

Why This Approach Stays Selective 

Because this early delivery takes real effort and investment on our behalf, we keep the process selective. We reserve early functional product development for organizations that show clear intent and strong alignment. The early artifact becomes the first shared step forward, rather than the first sales step. 

The Lasting Impact on Partnership Formation 

When you start by delivering something meaningful, you set the tone for everything that follows. The moment that first version hits the court, the moment you see the lift, the rim, and the finish, the entire relationship changes. 

In the end, the same lesson from basketball holds true. People do not remember the talk. They remember the dunk. And we would rather spend our time building something real than explaining why we could. 

If you want to explore what it looks like to begin with real work instead of a pitch, we would love to continue the conversation. Let’s talk. 

Key Takeaways 

• The evaluation gap is real: AI enables teams to build prototypes in 5-10 days, yet traditional enterprise evaluation still operates on 3-6 month timelines. This mismatch leaves buyers relying on promises instead of proof. 

• Most buyers decide before formal evaluation: 92% of B2B buyers start their journey with at least one vendor in mind, and 41% have already selected their preferred vendor before formal evaluation begins. Early proof matters more than polished presentations. 

• Partnership failures stem from misalignment, not capability: Enterprise AI implementations rarely fail due to weak engineering or design. They fail because teams hold different pictures of the same future, differences that stay hidden until it’s too late to course correct easily. 

• Functional products reveal what presentations cannot: A shared early version shows how a partner interprets requirements, handles real constraints, navigates tradeoffs, and collaborates under pressure. No deck can demonstrate these partnership dynamics. 

• Early functional delivery changes the conversation: When prospects interact with a working product built with their actual data, the conversation shifts from “Can you do this?” to “What else can we build together?” Trust forms through shared work, not sales process.

FAQs

How long does early functional delivery take to create? 

Early functional product delivery typically takes 5-10 days, depending on complexity and data availability. At Robots & Pencils, we focus on demonstrating how we interpret requirements, handle real constraints, and collaborate under actual conditions rather than achieving feature completeness. 

What makes this approach different from a proof of concept? 

Unlike traditional proofs of concept, our baseline iteration is built with the client’s actual data and reflects real-world constraints from day one. It demonstrates partnership dynamics and problem-solving approach, not just technical capability. 

Which types of organizations are best suited for this approach? 

Organizations that show clear intent, strong alignment on objectives, and readiness to engage collaboratively benefit most from early functional delivery. This approach works best when both parties are committed to testing the partnership through real work rather than presentations. 

Can this approach work for regulated industries like healthcare or financial services? 

Yes. We’ve successfully delivered early functional products for healthcare technology companies and financial services organizations. The approach adapts to industry-specific requirements while maintaining rapid delivery timelines. 

The post Product, not PowerPoint: How to Evaluate Enterprise AI Partners  appeared first on Robots & Pencils.

Robots & Pencils, an applied AI engineering partner known for high-velocity delivery and measurable business outcomes, today announced the opening of its Studio for Generative and Agentic AI in Bellevue.  

Candidates seeking high-impact engineering, data, and design roles can learn more at robotsandpencils.com/careers. 

A Strategic Expansion to Meet Demand for Rapid Enterprise AI 

The Studio in downtown Bellevue is fully operational and actively building its founding team as enterprise demand accelerates for AI systems that move from experimentation to production with speed, precision, and accountability. 

The Studio expands Robots & Pencils’ AI-native delivery model and represents a significant step in the company’s U.S. growth, supported by global operations in Cleveland, Calgary, Toronto, Bogota, and Lviv. It adds meaningful capacity to support organizations launching AI-enabled products, platforms, and agentic systems at scale. 

Strong Leadership Driving Focus and Velocity 

The Studio in Bellevue operates under the leadership of Jeff Kirk, Executive Vice President of Applied AI at Robots & Pencils, and reinforces the company’s growing presence in the Pacific Northwest while serving global clients pursuing ambitious AI initiatives. 

“This Studio is designed for builders who want real ownership and real impact,” said Kirk. “We are bringing together experienced teams who move quickly, think clearly, and take responsibility for outcomes. Our Studio model gives people the trust and focus to make strong decisions and deliver AI systems that translate directly into business value.” 

Working with AWS to Accelerate Enterprise AI Delivery 

As an Amazon Web Services Partner located near Amazon headquarters, the Studio in Bellevue supports clients building and scaling AI solutions on Amazon Bedrock, Amazon SageMaker, Amazon Bedrock AgentCore, Amazon Quick Suite, and related AWS services. This proximity strengthens collaboration and supports faster experimentation and production-ready delivery for complex enterprise environments. 

Robots & Pencils was recently selected as one of 11 inaugural partners in the invite-only AWS Pattern Partners program. The program works with a select group of consulting partners to define how enterprises adopt next-generation AI and emerging technologies on AWS through validated, repeatable patterns. 

This recognition acknowledges Robots & Pencils’ experience delivering production-grade AI architectures for enterprise customers. Working with AWS, the company supports secure and scalable AI delivery across regulated and high-impact industries while enabling teams to move with clarity and confidence from design through deployment. 

A Destination for Elite AI Builders 

The Studio for Generative and Agentic AI reflects Robots & Pencils’ long-standing commitment to talent density and engineering craft. Employees average fifteen years of experience and contribute patents, published research, and category-defining products across industries. The Studio in Bellevue offers engineers, applied AI specialists, product leaders, and user experience innovators the opportunity to shape a new hub while influencing high-stakes client work from the ground up. 

“To support our substantial client demand, we need incredible GenAI talent and are significantly investing in how we work with AWS. Our Bellevue AI Studio places our teams in close proximity to AWS, creating an environment that supports knowledge sharing and enables us to tap into the Seattle-area hot bed of incredible, wicked-smart talent,” said Len Pagon Jr., CEO of Robots & Pencils. “The Bellevue location expands our ability to deliver applied AI outcomes at scale while creating an environment where experienced builders can do the most meaningful work of their careers. This expansion reflects confidence in our teams and the direction we are taking the company.” 

Velocity Pods Deliver AI Products in Weeks 

Teams in the Studio operate in industry-focused Velocity Pods supporting Education, Energy, Financial Services, Healthcare, Manufacturing, Transportation, and Retail and CPG. These pods launch AI generative and agentic products to market in 30-to-45-day cycles while addressing complex modernization and intelligent automation programs across the enterprise. 

Now Hiring for AI Engineering Jobs in Bellevue 

Robots & Pencils is actively staffing the Studio for Generative and Agentic AI in Bellevue and invites experienced engineers and builders to apply. Open roles span engineering, applied AI, product, and design. 

Interested candidates can explore opportunities and submit applications at robotsandpencils.com/careers. 

The Studio in Bellevue opens with momentum, leadership, and a clear mandate to build AI solutions that matter.  

The pace of AI change can feel relentless with tools, processes, and practices evolving almost weekly. We help organizations navigate this landscape with clarity, balancing experimentation with governance, and turning AI’s potential into practical, measurable outcomes. If you’re looking to explore how AI can work inside your organization—not just in theory, but in practice—we’d love to be a partner in that journey. Request an AI briefing. 

The post Robots & Pencils Opens Studio for Generative and Agentic AI in Bellevue appeared first on Robots & Pencils.

The team Zoom call felt like an intervention. “Just try it,” they said. “Everyone open Claude Code.” My palms were sweating. Twenty years of visual design, and I’d only clumsily played around with code. I was the furthest thing from a developer you could imagine. 

Two hours later, I couldn’t stop. I’d built three working prototypes. My ideas, the ones that lived and died in Figma for years, were suddenly real. Interactive. Alive. 

This is the story of how I went from code-phobic to code-addicted in a single afternoon. And why every designer reading this is about to follow the same path. 

The Designer–Developer Divide 

For decades, we’ve accepted a fundamental lie: Designers design, developers develop. The gap between these worlds felt like a chasm requiring years of computer science education to cross. HTML, CSS, JavaScript were foreign languages spoken in basement servers and terminal windows. 

I believed this myth completely. My job was making things beautiful. Someone else’s job was making them work. This division of labor felt natural, inevitable, and even efficient. Why would I learn to code when developers already did it so well? 

That myth cost me every idea I couldn’t prototype myself, every interaction I couldn’t test, and every vision that got lost in translation. Twenty years of creative constipation, waiting for someone else to birth my ideas. 

Five Minutes to AI-Powered Prototyping 

“Open your terminal,” they said. Haha. I’d only ever really seen it used in The Matrix. The black window appeared. The cursor blinked in judgment. Type ‘claude’ and tell it what you want to build. 

My first prompt was embarrassingly simple: “Make me a color palette generator.” I expected nothing. Error messages, maybe. Definitely not working code. 

But there it was. A functioning app. My app. Built with my words. 

The next prompt came faster: “Add a feature that saves palettes locally.” Done. “Make the colors animate when they change.” Done. Each success made me braver. Each response made me hungrier. 

By the end of that call, I wasn’t just using AI to code. I was thinking in code. The barrier I’d spent two decades accepting had evaporated in minutes. 

The New Addiction: Vibe Coding 

They call it “vibe coding,” this conversational dance with AI. You describe what you want. The AI builds it. You refine. It rebuilds. No syntax to memorize. No documentation to parse. Just pure creative expression flowing directly into functional reality. 

I became obsessed. That first night, I built seven prototypes. Not because anyone asked. Not because I needed them. Because I could. Every design idea I’d shelved, every interaction I’d dreamed about was suddenly possible. 

The feeling was intoxicating. After years of creating static mockups, watching my designs move and respond felt like gaining a superpower. Click this button, trigger that animation. Hover here, reveal that detail. My aesthetic decisions instantly became experiential. 

When Designers Start Coding 

Something profound happens when the person with design taste controls implementation. The endless back-and-forth disappears. The “that’s not quite what I meant” conversations vanish. The design is the product is the code. 

UXPin’s research shows designers can now “generate fully functional components with just a few inputs.” But that clinical description misses the emotional reality. It’s not about generating components. It’s about giving creative vision direct access to digital reality. 

I started noticing details I’d never considered before. The precise timing of transitions. The subtle response to user actions. The difference between functional and delightful. When you control every aspect of implementation, you start designing differently. You start designing more ambitiously, more precisely, and with more courage.  

AI Code Tools That Make It Possible 

The technology enabling this transformation is staggering. Visual Copilot converts Figma designs directly to React code. Codia processes designs 100x faster than manual coding. These aren’t incremental improvements. They’re paradigm shifts disguised as product features. 

But the tools are just enablers. The real revolution happens in your mind. That moment when you realize the prison was self-imposed. The guards were imaginary. The key was always in your pocket. 

Natural language is the new programming language. If you can describe what you want, you can build it. If you can envision it, you can ship it. The only barrier left is imagination. 

The Future of Designer-Coders 

Organizations clinging to traditional designer-developer divisions are about to face a reckoning. While they coordinate handoffs and manage miscommunications, designers who code are shipping. Iterating. Learning. Building. 

This shift amplifies designers. Developers can focus on complex systems and architecture. Designers can implement their vision directly. Everyone works at a higher level of abstraction and impact. 

The competitive advantage is obvious. Teams with designer-coders ship better products faster. Not because they’re more efficient, but because they’re more effective. Vision and execution unified in a single mind. 

Your First Steps with AI Coding 

I know what you’re thinking. “But I’m not technical.” Neither was I. “But I don’t understand programming.” You don’t need to. “But I’m just a designer.” That’s exactly why you’re perfect for this. 

The same skills that make you a great designer, understanding users, crafting experiences, and obsessing over details, make you a natural at AI-powered development. You already think in systems and interactions. Now you can build them. 

Start small. Open a terminal and type a prompt. Build something stupid. Then build something slightly less stupid. Within hours, you’ll be building things that matter. Within days, you’ll wonder how you ever worked without this power. 

The Designer You’ll Become with AI 

Six months later, I barely recognize my old workflow. Static mockups feel like cave paintings. Design documentation seems like elaborate fiction. The idea of handing off my vision for someone else to interpret? Unthinkable. 

My role hasn’t changed. I’m still a visual designer. But my capability has transformed. I create experiences versus just imagining them. I propose ideas and prove them. I don’t just design products and ship them. 

The code anxiety is gone. Every limitation that once constrained me now seems artificial. The only question left is what to build next. 

Your journey starts with a single prompt. What will yours be? 

The pace of AI change can feel relentless with tools, processes, and practices evolving almost weekly. We help organizations navigate this landscape with clarity, balancing experimentation with governance, and turning AI’s potential into practical, measurable outcomes. If you’re looking to explore how AI can work inside your organization—not just in theory, but in practice—we’d love to be a partner in that journey. Request an AI briefing. 

Key Takeaways 

• AI code tools collapse the designer–developer divide, letting designers build functional prototypes in hours. 

• Natural language is becoming the new programming language, enabling creativity without technical gatekeeping. 

• **The emotional shift is as important as the technical one—**designers feel empowered, ambitious, and free to experiment. 

• Organizations that embrace designer-coders gain speed and competitive advantage, while traditional handoff models risk lagging. 

• The real revolution is mindset: imagination no longer stops at static mockups—it moves directly into working systems. 

FAQs 

Q: What are AI code tools? 
AI code tools (like Claude Code, GitHub Copilot, or Visual Copilot) let you describe what you want in natural language, then generate working code automatically. 

Q: How can designers use AI code tools? 
Designers can turn Figma mockups or written prompts into functional prototypes, animations, and interactions—without learning traditional programming. 

Q: Does this replace developers? 
No. Developers focus on complex architecture, scaling, and systems. AI coding empowers designers to own interaction and experience details, speeding collaboration. 

Q: Why does this matter for organizations? 
Teams that adopt AI prototyping iterate faster, align design and development more tightly, and ship higher-quality products with fewer miscommunications. 

Q: What skills do designers need to start? 
Curiosity and creativity. If you can describe an idea clearly, you can build it with AI code tools. 

The post How I Learned to Stop Worrying and Love AI Code: A Designer’s Journey  appeared first on Robots & Pencils.

Three sprints later, what comes back looks… different. Not wrong exactly, but not right either. The spacing feels off. The animations lack finesse. That subtle gradient you agonized over? Gone. The developer followed your specs perfectly, yet somehow the soul got lost in translation. 

Designers have always accepted this degradation as the cost of building digital products. We tried creating processes to minimize it, like design tokens, component libraries, and endless documentation, but we never stopped to question the handoff itself. 

Until now. AI just made the entire ritual obsolete. 

AI Ends the Design Handoff 

The design-to-development pipeline has always been messy, more like a game of telephone in a storm than a straight line. A designer’s vision turns into static mockups, those mockups get turned into specs, and then the specs are coded by someone who wasn’t there when the creative calls were made. 

Every step adds noise. Every handoff blurs the details. By the time the design reaches a user, the intent has been watered down through too many layers of translation. To manage the loss, we added layers. Product managers translate between teams, QA engineers catch mistakes, and design systems impose order. But taste cannot be standardized. 

AI design-to-code tools eliminate this process entirely. When a designer can move directly from Figma to functional code, the telephone line disappears. One vision, one implementation, and zero interpretation. 

Developers Spend Half Their Time on UI 

Here’s a truth we rarely say out loud. Developers spend 30–50% of their time on UI implementation. They’re not solving tough algorithms or designing big system architectures. They’re taking what’s already laid out in Figma and turning it into code. It takes skill and attention, but it’s work that repeats more than it invents. 

I’m not criticizing developers. I’m criticizing this process. We’ve asked our most technical team members to spend a third of their time as human transpilers, converting one formal language (design) into another (code). The real tragedy? They’re good at it. So good that we never stopped to ask if they should be doing it at all. 

When Airbnb started generating production code from hand-drawn sketches, they weren’t just saving time. They were liberating their engineers to focus on problems that actually require engineering. 

The Rise of the Tastemaker-Maker 

Something big shifts when designers can bring their own vision to life. The feedback loop shrinks from weeks to minutes. When something doesn’t look right, you can fix it immediately. If inspiration strikes, you can send it to staging and get real reactions in hours instead of weeks. What used to take whole sprints now fits inside a single coffee break. 

It’s tempting to frame this as designers turning into developers, but that misses the point. What’s really happening is that taste itself can now be put into action. The person who knows why a button feels right at 48 pixels, or why an animation needs a certain ease, or why an error state demands a particular shade of red, can actually make those choices real. 

That shift is giving rise to a new kind of role: the tastemaker-maker. They’re not confined to design or development but move fluidly between both. They hold the vision and the skills to bring it to life. They think in experiences and build in code. 

What Happens When Handoffs Disappear 

The implications ripple outward. When handoffs disappear, so do the roles built around managing them. The product manager who translates between design and development. The QA engineer who catches implementation mismatches. The technical lead who estimates UI development time. 

Teams start reorganizing around vision rather than function. Instead of design teams and development teams, you get product teams led by tastemaker-makers who can move from concept to code without translation. Supporting them are engineers focused on what AI can’t do: solving novel technical challenges, building robust architectures, optimizing performance at scale. 

This is job elevation. Developers stop being expensive markup translators and become true engineers. Designers stop being documentation machines and become product builders. Everyone moves up the value chain. 

AI Design to Code Speeds Shipping 

Companies using AI design-to-code tools report shipping features 3x faster with pixel-perfect accuracy. That’s a step function change in capability. While your team is still playing telephone, your competitors are shipping experiences that feel inevitable because they were never compromised by translation. 

The gap compounds daily. Each handoff you eliminate saves time on that project and builds institutional knowledge about what becomes possible when vision and execution converge. Your competitors are shipping faster and learning faster. 

How to Reorganize Without Handoffs 

Adopting AI design-to-code tools is the easy part. The hard part is reimagining your organization without handoffs. Start here: 

Identify your tastemaker-makers. They already exist in your organization. These are the designers who code on the side with strong aesthetic sense. Give them AI tools and watch them soar. 

Reorganize around products, not functions. Small teams with end-to-end ownership beat large teams with perfect handoffs every time. 

Measure differently. Stop counting tickets closed and start counting experiences shipped. Quality and velocity aren’t tradeoffs when the same person owns both. 

The End of the Design Handoff Era 

The design handoff was a bug in digital product development. A workaround for the technological limitation that the person who could envision the experience couldn’t build it. That limitation just died, and with it, an entire way of working that we tolerated for so long we forgot it was broken. 

The future belongs to those who can both dream and deliver. The handoff is dead. Long live the makers. 

The pace of AI change can feel relentless with tools, processes, and practices evolving almost weekly. We help organizations navigate this landscape with clarity, balancing experimentation with governance, and turning AI’s potential into practical, measurable outcomes. If you’re looking to explore how AI can work inside your organization—not just in theory, but in practice—we’d love to be a partner in that journey. Request an AI briefing. 

Key Takeaways 

• The traditional design-to-development handoff created costly information loss and slowed iteration. 

• AI design-to-code tools eliminate the handoff, enabling designers to move directly from vision to implementation. 

• Developers spend up to 50% of their time on UI translation—AI liberates them for higher-value engineering. 

• A new role is emerging: the tastemaker-maker, who blends design taste with the ability to build. 

• Teams must reorganize around product vision rather than functional silos to stay competitive. 

FAQs 

What is a design handoff? 
The process where designers deliver mockups and specifications to developers, who then translate them into code. 

Why is the handoff inefficient? Each translation from design to documentation to implementation introduces information loss, slowing delivery and compromising quality. 

How do AI design-to-code tools change the process? 
They allow direct conversion from design tools like Figma into functional code, eliminating the translation step. 

What is a tastemaker-maker? 
A hybrid role that combines a designer’s vision with the ability to implement in code, collapsing feedback loops and accelerating iteration. 

Does this replace developers? 
No. It elevates developers to focus on complex engineering challenges, while routine UI translation is handled by AI. 

What’s the business impact? 
Companies using these tools report shipping 3x faster with higher fidelity—creating both a speed and learning advantage. 

The post The Death of the Design Handoff: How AI Turns Tastemakers into Makers  appeared first on Robots & Pencils.

For research leaders, that changes the question. We have always studied humans. But when an agent performs half the task, who is the user? 

Agents on the Front Lines of Experience 

AI agents reveal truths that interviews cannot. Their activity logs expose where systems succeed and where they stumble. A rerouted request highlights a friction point. A repeated error marks a design flaw. Escalations and overrides surface moments where human judgment still needs to intervene. These are not anecdotes filtered through memory. They are live records of system behavior. 

And that’s why we need to treat agents as participants in their own right. 

A New Kind of Participant 

Treating agents as research participants reframes what discovery looks like. Interaction data becomes a continuous feed, showing failure rates, repeated queries, and usage patterns at scale. Humans remain the primary source of insight: the frustrations, the context, and the emotional weight. Agent activity adds another layer, highlighting recurring points of friction within the workflow and offering evidence that supports and extends what people share. Together, they create a more complete picture than either could alone. 

Methodology That Respects the Signal 

Of course, agent data is not self-explanatory. Logs are noisy. Bias can creep in if models were trained on narrow datasets. Privacy concerns must be addressed with care. The job of the researcher remains critical: separating signal from noise, validating patterns, and weaving human context into machine traces. Instead of replacing human perspective, agent data can enrich and ground it, adding evidence that makes qualitative insight even stronger. This reframing doesn’t just affect research practice, it also changes how we think about design. 

Designing for Multi-Actor Systems 

Products are no longer built for humans alone. They must work for the people who use them and the agents that increasingly mediate their experience. A customer may never touch a form field if their AI assistant fills it in. An employee may never interact directly with a dashboard if their agent retrieves the results. Design must account for both participants. 

Organizations that learn to research this new ecosystem will see problems sooner, adapt faster, and scale more effectively. Those that continue to study humans alone risk optimizing for only half the journey. 

The New Research Frontier 

Research has always been about listening closely. Today, listening means more than interviews and surveys. It means learning from the digital actors working beside us, the agents carrying out tasks, flagging failures, and amplifying our actions. 

The user is no longer singular. It is human and machine together. Understanding both is the only way to design systems that reflect the reality of work today. 

This piece expands the very definition of the user. For the other shifts redefining research, see our earlier explorations on format, how to move beyond static deliverables, and scope, how AI dissolves the depth vs. breadth tradeoff. 

The pace of AI change can feel relentless with tools, processes, and practices evolving almost weekly. We help organizations navigate this landscape with clarity, balancing experimentation with governance, and turning AI’s potential into practical, measurable outcomes. If you’re looking to explore how AI can work inside your organization—not just in theory, but in practice—we’d love to be a partner in that journey. Request an AI briefing.   

Key Takeaways

• AI agents are no longer background tools; they now perform frontline tasks such as scheduling, routing, and managing workflows.
• Research has historically focused only on humans, but agents are now shaping experiences and surfacing friction points alongside people.
• Studying agents as supplemental participants provides evidence of “where” breakdowns occur, enriching human perspectives rather than replacing them.
• Researchers remain essential to interpret agent data, separate signal from noise, and ground findings in human context.
• Designing for multi-actor systems requires understanding both humans and the agents mediating their experiences.

FAQs

Why consider AI agents as research participants?
AI agents actively shape workflows and user experiences. Their activity logs reveal friction points, errors, and escalations that human feedback alone may miss. Including them as research participants offers a more complete picture of how systems actually perform.

Do AI agents replace human participants in research?
No. Humans remain the primary source of context, emotion, and motivation. Agent data adds a complementary layer of evidence, enriching and grounding what people already share.

What types of insight can AI agents provide?
Agents surface recurring points of friction, repeated errors, and escalation patterns. These signals highlight where workflows break down, offering evidence to support and extend human feedback.

What role do researchers play when analyzing agent data?
Researchers remain critical. They filter noise, validate patterns, address bias, and ensure agent activity is interpreted with proper human context. The shift broadens qualitative practice rather than replacing it.

What is a multi-actor system in research?
A multi-actor system is one where both humans and AI agents interact to complete tasks. Designing for these systems means studying the interplay between people and machines, ensuring both participants are accounted for.

How does including agents in research improve design?
By listening to both humans and agents, organizations can spot problems sooner, adapt faster, and create systems that reflect the true complexity of modern workflows.

The post AI Agents Are Users Too: Rethinking Research for Multi-Actor Systems  appeared first on Robots & Pencils.

This has always been the tradeoff, go deep with a few voices or broaden the scope and risk losing nuance. Leaders accepted that limitation as the cost of qualitative research. 

That ceiling is gone. 

The Ceiling Was Human Labor 

Generative research has always promised what numbers cannot capture, the story beneath the metric. But human synthesis is slow. Each new transcript multiplies complexity, until the process itself becomes the limiter. Teams stopped at 20 or 30 conversations not because curiosity ended, but because the hours to make sense of them did. Nuance gave way to saturation. 

Executives signed off on smaller studies and called it pragmatism. In truth, it was constraint. 

AI Opens the Door to Scale 

Large language models change the equation. Instead of weeks of sticky notes and clustering, AI can surface themes in hours. It highlights recurring ideas, connects outliers, and organizes insights without exhausting the team. The researcher’s role remains. Judgment still matters, but the ceiling imposed by human-only synthesis disappears. 

Instead of losing clarity as the number grows, each additional conversation now sharpens the signal, strengthening patterns, surfacing weak signals earlier, and giving leaders the confidence to act with richer evidence. 

Discovery Becomes Active 

The real breakthrough is not only scale, but also timing. With AI-enabled synthesis, insights emerge as the study unfolds. After the first dozen conversations, early themes are visible. Gaps in demographics or use cases show up while there is still time to adjust. By week two, the research is already feeding product decisions. 

Instead of waiting for a final report, teams get a living stream of discovery. Research shifts from retrospective artifact to active driver of strategy. 

Nuance at Speed 

For organizations, this ends the false binary. Depth and breadth no longer compete. A bank exploring new digital features can capture voices across demographics in weeks, not months. A health-tech team can fold dozens of patient experiences into the design cycle in real time. A software platform can test adoption signals across continents without sacrificing cultural nuance. 

The payoff is more than efficiency. It is confidence. When executives see both scale and nuance in the evidence, they act faster and with greater conviction. 

The New Standard 

The era of choosing between depth or breadth is behind us. AI frees research leaders from the constraints of small samples or limited perspectives. With AI as a synthesis partner, the standard shifts: hundreds of voices, interpreted with clarity, delivered at speed. 

For teams still focused on fixing the format problem, our previous piece, The $150K PDF That Nobody Reads, explores how static reports constrain research. Our next article examines an even bigger shift: what happens when your users are no longer only people.

The pace of AI change can feel relentless with tools, processes, and practices evolving almost weekly. We help organizations navigate this landscape with clarity, balancing experimentation with governance, and turning AI’s potential into practical, measurable outcomes. If you’re looking to explore how AI can work inside your organization—not just in theory, but in practice—we’d love to be a partner in that journey. Request an AI briefing.   

Key Takeaways

• Qualitative research has historically forced a choice between depth (few voices, rich detail) and breadth (many voices, less nuance).
• Human-only synthesis becomes a bottleneck after 20–30 interviews, creating the illusion that small samples are “pragmatic.”
• AI-enabled synthesis dissolves that tradeoff by analyzing hundreds of conversations with clarity, surfacing patterns and weak signals at scale.
• Discovery shifts from a retrospective report to an active, ongoing process that informs decisions while research is still in motion.
• Organizations that embrace this model gain faster, more confident decision-making grounded in both depth and scale.

FAQS

What is the depth vs. breadth tradeoff in qualitative research?
The depth vs. breadth tradeoff refers to the long-standing belief that teams must choose between conducting a small number of interviews with rich nuance (depth) or a larger sample with less detail (breadth). Human synthesis struggles to handle both simultaneously, forcing this choice.

How does AI change the depth vs. breadth tradeoff?
AI dissolves the tradeoff by enabling researchers to process hundreds of conversations quickly while still preserving nuance. Instead of diluting insight, scale strengthens pattern recognition and surfaces weak signals earlier.

Why has qualitative research been constrained to small sample sizes?
Human synthesis is time-consuming. After 20–30 interviews, transcripts become overwhelming, and important signals get lost in the noise. This labor bottleneck led leaders to view small samples as “pragmatic,” even though it was really a constraint of capacity.

Does AI replace the role of the researcher?
No. AI accelerates synthesis, but the researcher remains critical for judgment, interpretation, and ensuring context and nuance are applied correctly. AI acts as a partner that expands capacity rather than a replacement.

What is the impact of AI-enabled synthesis on decision-making?
With faster synthesis and preserved nuance, research insights emerge in real time rather than only in final reports. Leaders gain richer evidence earlier, which supports faster, more confident decisions.

What does this mean for the future of qualitative research?
The old tradeoff between depth and breadth is over. AI makes it possible to achieve both simultaneously, shifting the standard for research to hundreds of voices interpreted with clarity and delivered at speed.

The post How AI Ends the Depth vs. Breadth Research Tradeoff  appeared first on Robots & Pencils.

It’s every researcher’s quiet fear. The initiative they poured months of work, a chunk of their sanity, and about a thousand sticky notes into becomes shelf-ware. Just another artifact joining strategy decks and persona posters that never found their way into real decisions. 

This is the way research has been delivered for decades, by global consultancies, boutique agencies, and yes, even by me. At $150K a report, it sounds extravagant. But when you consider the sheer effort, the rarity of the talent involved, and the stakes of anchoring business decisions in real customer insight, it’s not hard to see why leaders sign the check. 

The issue isn’t the value of the research. It’s the belief that insights should live in documents at all. 

Research as a Living System 

Now picture a different moment. The same executive doesn’t reach for a drawer. She opens her laptop and types: “What causes the most friction when ordering internationally?” 

Within seconds she’s reviewing tagged quotes from dozens of interviews, seeing patterns of friction emerge, even testing new messaging against synthesized persona responses. The research isn’t locked in a PDF. It’s alive, queryable, and in motion. 

This isn’t a fantasy. It’s the natural evolution of how research should work: not as one-time deliverables, but as a living system. 

The numbers show why change is overdue. Eighty percent of Research Ops & UX professionals use some form of research repository, but over half reported fair or poor adoption. The tools are frustrating, time consuming to maintain, and lack ownership. Instead of mining the insights they already have, teams commission new studies, resulting in an expensive cycle of creating artifacts that sit idle, while decisions move on without them. 

It’s a Usability Problem 

Research hasn’t failed because of weak insights. It’s been constrained by the static format of reports. Once findings are bound in a PDF or slide deck, the deliverable has to serve multiple audiences at once, and it starts to bend under its own weight. 

For executives, the executive summary provides a clean snapshot of findings. But when the time comes to make a concrete decision, the summary isn’t enough. They have to dive into the hundred-page appendix to trace back the evidence, which slows down the moment of action. 

On the other hand, product teams don’t need summaries, they need detailed insights for the feature they’re building right now. In long static reports, those details are often buried or disconnected from their workflow. Sometimes they don’t even realize the answer exists at all, so the research goes unused, or even gets repeated. An insight that can’t be surfaced when it’s needed might as well not exist. 

The constraint isn’t the quality of the research. It’s the format. Static deliverables fracture usability across audiences and leave each group working harder than they should to put insights into play. 

Research as a Product 

While we usually view research as an input into products, research itself is a product too. And with a product mindset, there is no “final deliverable,” only an evolving body of user knowledge that grows in value over time. 

In this model, the researcher acts as a knowledge steward of the user insight “product,” curating, refining, and continuously delivering customer insights to their users: the executives, product managers, designers, and engineers who need insights in different forms and at different moments. 

Like any product, research needs a roadmap. It has gaps to fill, like user groups not yet heard from, or behaviors not yet explored. It has features to maintain like transcripts, coded data, and tagged insights. And it has adoption goals, because insights only create value when people use them. 

This approach transforms reports too. A static deck becomes just a temporary framing of the knowledge that already exists in the system. With AI, you can auto-generate the right “version” of research for the right audience, such as an executive summary for the C-suite, annotations on backlog items for product teams, or a user-centered evaluation for design reviews. 

Treating research as a product also opens the door to continuous improvement. A research backlog can track unanswered questions, emerging themes, and opportunities for deeper exploration. Researchers can measure not just delivery (“did we produce quality insights?”) but usage (“did the insights influence a decision?”). Over time, the research “product” compounds in value, becoming a living, evolving system rather than a series of static outputs. 

This new model requires a new generation of tools. AI can now cluster themes, surface patterns, simulate persona responses, and expose insights through natural Q&A. AI makes the recomposition of insights into deliverables cheap. That allows us to focus on how our users get the insights they need in the way they need them. 

From Deliverable to Product 

Treating research as a product changes the central question. It’s no longer, “What should this report contain?” but “What questions might stakeholders need to answer, and how do we make those answers immediately accessible?” 

When research is built for inquiry, every transcript, survey, and usability session becomes part of a living knowledge base that compounds in value over time. Success shifts too: not in the number of reports delivered, but in how often insights are pulled into decisions. A six-figure investment should inform hundreds of critical choices, not one presentation that fades into archives. 

And here’s the irony: the product mindset actually produces better reports as well. When purpose-built reports focus as much on their usage as the information they contain, they become invaluable components of the software production machine. 

Research itself isn’t broken. It just needs a product mindset and AI-based qualitative analysis tools that turns insights into a living system, not a slide deck. 

Next in the series, we look at two more shifts: AI removing the depth vs. breadth constraint, and the rise of agents as research participants.

The pace of AI change can feel relentless with tools, processes, and practices evolving almost weekly. We help organizations navigate this landscape with clarity, balancing experimentation with governance, and turning AI’s potential into practical, measurable outcomes. If you’re looking to explore how AI can work inside your organization—not just in theory, but in practice—we’d love to be a partner in that journey. Request a strategy session.  

Key Takeaways

• Traditional research deliverables, like lengthy reports and slide decks, often expire the moment they are delivered, leaving insights unused.
• The problem is not weak research but static formats that fracture usability across executives, product teams, and designers.
• Treating research as a product reframes it as a living system: evolving, queryable, and compounding in value over time.
• With a product mindset, researchers become knowledge stewards, curating and delivering insights in forms tailored to each audience.
• AI enables this shift by clustering themes, surfacing patterns, and recomposing deliverables dynamically, making insights immediately accessible.

FAQs

What is the problem with traditional research reports?
Traditional reports often serve as static artifacts. Once published, they struggle to meet the needs of multiple audiences and quickly become outdated, limiting their impact on real decisions.

Why is research often underutilized in organizations?
Research is underutilized because its insights are locked in formats like PDFs or decks. Executives, product teams, and designers often cannot access the right detail at the right time, so findings go unused or studies are repeated.

What does it mean to treat research as a product?
Treating research as a product means building a continuously evolving knowledge base rather than one-time deliverables. Insights are curated, updated, and delivered in forms that align with the needs of different stakeholders.

How does AI support this new model?
AI makes it possible to cluster themes, surface weak signals, and generate audience-specific deliverables on demand. This reduces maintenance overhead and ensures insights are always accessible when needed.

What role do researchers play in this model?
Researchers become knowledge stewards, ensuring the insight “product” is accurate, relevant, and continuously improved. Their work shifts from producing final reports to curating and delivering insights that compound in value over time.

How does this benefit organizations?
Organizations gain faster, more confident decision-making. A six-figure research investment can inform hundreds of decisions, rather than fading after a single presentation.

The post The $150K PDF That Nobody Reads: From Research Deliverables to Living Systems  appeared first on Robots & Pencils.