
Mobility

Automotive | Prototyping Bucks & Demonstrators
Category
Expertise
Teague designed and built three adaptable automotive prototypes that gave development teams new ways to explore and evaluate emerging vehicle experiences.
CHALLENGE
Automakers have long relied on physical bucks to evaluate vehicle designs. These full-scale mockups recreate the dimensions and key features of a vehicle, allowing teams to test what can't be fully understood on a screen. Most are sophisticated engineering environments, built to support extensive development and validation.
But the demands on physical prototyping are changing as the shift toward software-defined vehicles reshapes automotive development. Software teams need to evaluate evolving experiences across different vehicle platforms, while innovation teams are exploring new ways of using the space inside a vehicle. Traditional, full-scale bucks aren't the most practical tools for this work, particularly when ideas are still taking shape.
Across three projects, automotive development teams turned to Teague for prototypes that could support the work without the complexity of building an entire vehicle. Each project presented a different challenge.

APPROACH
A buck isn't just a representation of a vehicle. It's a tool for making ideas tangible, built around what a team needs to explore, evaluate, or understand.
Designing the prototype meant thinking beyond the physical experience. Each structure had to account for how it would be used and where it would live.
Getting that balance right shaped each project. The relationship between a driver and a display, for example, needs to feel accurate when evaluating in-vehicle software. But the surrounding structure doesn't need the appearance or functionality of a finished car.
Teague used production parts where their dimensions and functionality mattered, alongside simpler components and construction methods that allowed the prototypes to change. Keeping some elements deliberately unfinished also helped direct attention to the experience under evaluation rather than details that weren't yet relevant.
Just as important was what happened after the prototypes left the workshop. These requirements influenced the engineering from the beginning, making each prototype practical to use as development continued.
Explore how prototyping brings emerging ideas into focus and helps teams make more informed design decisions.

SOLUTION
An automotive software team had developed concepts for in-vehicle screen experiences, but nothing physical to test them in. The software needed to work across different vehicle platforms, each with its own relationship between the driver, dashboard, and displays.
The buck's modular design allowed multiple vehicle configurations to be tested without rebuilding the structure.
The resulting ergonomic buck recreated the cockpit and front-row seating on raised decks. Its adjustable dashboard, steering wheel, and seating positions allowed the same structure to accommodate different vehicle layouts, including left- and right-hand drive.
Designed to move through standard office doors and elevators, the buck could be installed directly in the client's studio rather than requiring a dedicated testing facility. Initial assembly took approximately two weeks, followed by a single day of installation.
There, the buck became part of the team's development process. Designers and developers could evaluate evolving software experiences in a physical cockpit, while colleagues in other countries participated in reviews using the same reference environment. The shared setup gave teams a more consistent way to evaluate experiences across studios as the software continued to evolve.


The second project emerged after members of another automotive innovation team saw the ergonomic cockpit and recognized a similar need within their own development program.
The 19-foot cargo van buck was designed to break down and ship on standard pallets, eliminating the need for specialized shipping.
Their interest was in commercial cargo vans, particularly how their interiors could be adapted for different applications. The team needed a full-scale environment to examine the spatial and functional details of the cargo area.
Teague built a 19-foot research buck that recreated the van's interior and exterior geometry, providing a realistic environment for evaluating different commercial uses. The completed buck supported research sessions with third-party vehicle upfitters, allowing the team to observe how they approached the cargo space and explore opportunities for customization.
The structure was designed to break down and ship on standard pallets, avoiding the specialized shipping requirements of a conventional full-scale build. Its modular construction also allowed the interior to be modified as the research progressed.




The original software team returned with a different ask. They needed a way to demonstrate their software-defined vehicle and human-machine interface experiences to executives without bringing an entire cockpit into the room.
The modular structure is designed to separate for transport and come together in six steps, with a target setup time of less than 30 minutes.
The biggest constraint was travel. The demonstrator needed to accompany the team on business trips while retaining the physical elements necessary to experience the software. Just as important, it couldn't compete with the interfaces it was built to showcase.
Teague developed a portable desktop demonstrator using the client's own steering wheel and primary vehicle displays. A powder-coated steel structure supports the wheel and instrument display, while the center screen sits on a separate adjustable stand. Matte-black finishes and 3D-printed components keep the focus on the software experience.
The modular structure is designed to separate for transport and come together in six steps, with a target setup time of less than 30 minutes. Components can also be updated as new vehicle concepts emerge.
Still in development, the demonstrator is scheduled for delivery later this year.