Skip to main content

Tiger Teams

Collaborative, specialized teams to solve real design and usability problems.

Thank you for your interest in joining a Tiger Team! A Tiger Team is “a specialized, cross-functional team brought together to solve or investigate a specific problem or critical issue.” What is a Tiger Team?


Team Name Team Members
Indicators & Selected States Calling candidates soon!
Footers Calling candidates soon!
High-Contrast Color Theme Calling candidates soon!


Team Name Team Members Start Date
Wizards s. Farhat, E. Ball-Babois, C. Cueller, C. Rodrigues 02/15/2024
User Profile Dropdown Menu N. Cadsawan, G. Assi, A. Chandroo, J. Dong, A. Galstyan, K. Phillips 07/17/2023
Advanced Table Features M. Brinkman, B. Brunner, N. Cadsawan, (M. Casale), C. Cuellar, (S. Farhat), A. Infante, W. Mezo-Gadia, K. Nguyen, J. Parr, C. Rodriguez, Krithika S, Z. Ward 05/18/2023
Animations & Microinteractions 2.0 W. Mezo-Gadia, J. Blackwell, S. Farhad, M. Manders, T. Manham, Z. Ward, D. Zambrano 05/18/2023


Team Name Team Members Status
Skeletons, Placeholders & Empty States R. Stillwell, J. de Wit, S. Farhat, I. Hong, M. Lee, M. Nawaz, C. Swilley In Production
Alerts, Messages, Notifications, and Toasts A. Chandroo, J. Blackwell, E. Gunther, M. Johns, M. Manders, T. Ortiz, V. Sridharan, Priyanka V R In Production
Accordions, Cards, Modals, and Tabs Z. Ward, K. Ponpandian, J. de Wit, A. Galstyan, E. Gunther, S. Kumar, T. Priya, M. Randrianavony, Krithika S., C. Shaw, Vimal A.V. In Production
Layout Tiger Team C. Cuellar, N. Cadsawan, R. Henness, Q. Le, T. Manham, M. Nawaz, C. Oliff, Purushothaman G. In Production
Desktop Patterns J. Kerbs, A. Bikic, P. Borgstein, K. Davies, L. Kause, C. Krieg, T. Sippola In Production
Microinteractions & Animations T. Manham, B. Choy, S. Farhat, J. Jyan, S. Kaukonen, W. Mezo-Gadia, T. Ortiz, D. Zambrano, (L. Galle, C. Oliff) In Production
Side Panel J. de Wit, C. Cuellar, A. Galstyan, D. Silcock Complete
Accessibility C. Koga, D. Bedick, A. Chammoth-Sivaraman, A. Chandroo, K. Davies, S. Farhad, J. Gray, G. Jagadeesan, S. Kaukonen, B. Kobloth, F. Kuipers, F. Lira, B. Mergener, C. Oliff, S. Paasch, I. Perez, A. Rodriguez, C. Rodriguez, H. Sunny Complete
Help Menu Navigation C. Christison, D. Bedick, A. Chammoth Sivaraman, M. Cowley, C. Cuellar, F. Kuipers, A. Galstyan, T. Hautalahti, M. Linja-aho, R. Pekkinen, C. Starbird, T. Stryker, K. Vander Ploeg, J. Wegerer Complete
Icon Revision & Review E. Gunther, G. Assi, S. Kaukonen, J. Kerbs, T. Manham, T. Ortiz, S. Reda, L. Saenz Complete
3D Design Patterns P. Borgstein, D. Bedick, D. Donnell, F. Keks, T. Kluyskens, A. Komninos, J. Oczkowski, E. Pilke, S. Sidhu, D. Silcock, T. Sippola, K. Thurlow Complete
Mobile Patterns D. Bedick, E. Bohn, N. Cadsawan, E. Gunther, I. Perez, J. A. Provin Silva, L. Saenz, C. Starbird, R. Stillwell Complete
Side Navigation J. Wittmeyer, N. Cadsawan, E. Deleon, E. Gunther, P. Karukkuvel, T. Manham, L. Meskanen-Kundu, C. D. Savio Lazaro, S. Taylor, A. Tucker, J. de Wit Complete
Dark Mode S. Kaukonen, P. Borgstein, E. Gunther, M. Johns, U. Meza, K. Phillips, A. C. Sivaraman, T. Williams, J. de Wit Complete
Icon Implementation S. Kaukonen, E. Deleon, E. Gunther, C. Krieg, T. Manham, S. Ortiz, A. Shchegoleva, N. Vasudevan Complete
Tables G. Leuhof, D. Donnell, H. Keller, S. Lucey, T. Manham, T. Ortiz, G. Piltzer, K. Tran, Z. Tran Do, S. Williams Complete
Header/ Top Nav S. Williams, N. Cadsawan, C. Christison, J. Dong, E. Gunther, S. Taylor, K. Tran Complete
Email Templates Z. Kulpa, T. Barnard, J. Dong, T. Saunders Complete
Data Visualization E. Nowak, T. Barnard, E. Bohn, C. Willis Complete
Icon Definitions S. Kaukonen, S. Bali, M. Heighway, T. Manham, E. Nowak Complete
Typography L. Cook, E. Bohn, A. Eidam, E. Gunther, M. Heighway, G.Leuhof, N. Springer Complete

Tiger Team Process

Tiger Team Process

1. Answer the call!

When the Modus team identifies a pattern or component that needs to be added to Modus, Trimble UX community is notified (via email, chat, and newsletter on the Modus website) soliciting Tiger Team members. In order to be part of the team, you should

  • have some expertise on the subject,
  • be currently working on the component on your product team,
  • or have vested interest in the component because of its prevalence in the product you are working on


  • have some time you can devote to the project (2-4 hours per week).

Once you express your interest, you will be invited to a kick-off meeting and the Modus Product Manager will contact your manager (if needed) to secure permission to divide your time between your team and the design system.

2. Review of candidates

The Modus Product Manager will review the volunteers to make sure the team has a good representation from different division.

3. Kick-off meeting

You will attend an introductory session to discuss the problem the team is going to solve, acceptance criteria, responsibilities, submission guidelines, set up a schedule for regular meetings, and agree on a tentative deadline. During the meeting, the team will also choose a leader.

4. Working sessions

The team members will meet weekly to collaborate on the best way to solve the problem and provide recommendations taking under consideration the needs of other divisions. They will also communicate through a group chat to share ideas, files, and information. Your enthusiasm is prerequisite, but your diligence in putting in the work and actively participating is the key to your team’s success.

5. Recommendation reviews

Once the team feels they have a good recommendation, they will share it with the Modus Product Manager, who will make sure that all the acceptance criteria are met. Then the leader will present the documentation and proposed designs to the Modus delivery team and/or the UX Board.

6. Revisions and publication

The team will address any objections and provide revisions to their recommendations. If no revisions are necessary, the component is going to move into production to be added to Modus. A pattern is accepted, when

  • It meets acceptance criteria;
  • It is in agreement with foundations and Modus style;
  • It passes the heuristic review criteria without any recommendations.

7. UX Community feedback

The UX community will have two weeks to review the recommendation, to conduct a heuristic evaluation, and to provide feedback. The feedback and any objections will be documented, discussed, and shared with the Tiger Team leader. Revisions will be prioritized for the next iteration.

Congratulations! You are a Modus hero!

We will reach out to the community, when we need volunteers. Please, visit the backlog to see what’s coming up or contact us.