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?
Tiger Teams
| Status | Team Name | Team Members | Start Date |
|---|---|---|---|
| Upcoming | Indicators & Selected States | Calling candidates soon! | |
| Upcoming | Microinteractions & Animations | Calling candidates soon! | |
| Upcoming | Side Panel | J. de Wit; Calling for more candidates soon! | |
| Active | Accessibility | C. Koga, D. Bedick, A. Chammoth-Sivaraman, A. Chandroo, K. Davies, J. Gray, G. Jagadeesan, B. Kobloth, F. Kuipers, F. Lira, B. Mergener, C. Oliff, S. Paasch, A. Rodriguez, C. Rodriguez | 04/25/2022 |
| Active | Help Menu Navigation | C. Christison, R. Pekkinen, A. Chammoth Sivaraman, A. Galstyan, C. Cuellar, D. Bedick, F. Kuipers, J. Wegerer, M. Cowley, C. Starbird, K. Vander Ploeg | 03/09/2022 |
| Active | 3D Design Patterns | P. Borgstein, A. Komninos, J. Oczkowski, D. Bedick, D. Donnell, F. Keks, T. Kluyskens, T. Sippola, E. Pilke, S. Sidhu, D. Silcock, K. Thurlow | 01/24/2022 |
| Active | Mobile Patterns | D. Bedick, E. Bohn, R. Stillwell, N. Cadsawan, C. Starbird, L. Saenz, E. Gunther, J. A. Provin Silva | 03/12/2021 |
| Inactive | Dark Mode | S. Kaukomen, A. C. Sivaraman, E. Gunther, J. de Wit, K. Phillips, M. Johns, P. Borgstein, T. Williams, U. Meza | In Production |
| Inactive | Icon Implementation | S. Kaukomen, T. Manham, A. Shchegoleva, C. Krieg, E. Deleon, E. Gunther, N. Vasudevan, S. Ortiz | In Production |
| Inactive | Side Navigation | J. Wittmeyer, C. D. Savio Lazaro, S. Taylor, J. de Wit, E. Gunther, T. Manham, N. Cadsawan, P. Karukkuvel, E. Deleon, A. Tucker, L. Meskanen-Kundu | In Production |
| Inactive | Tables | G. Leuhof, D. Donnell, G. Piltzer, H. Keller, K. Tran, S. Lucey, S. Williams, T. Ortiz, T. Manham, Z. Tran Do | In Production |
| Inactive | Header/ Top Nav | S. Williams, C. Christison, E. Gunther, J. Dong, K. Tran, N. Cadsawan, S. Taylor | Complete |
| Inactive | Email Templates | Z. Kulpa, J. Dong, T. Barnard, T. Saunders | Complete |
| Inactive | Data Visualization | E. Nowak, C. Willis, E. Bohn, T. Barnard | Complete |
| Inactive | Icon Definitions | S. Kaukomen, S. Bali, T. Manham, M. Heighway, E. Nowak | Complete |
| Inactive | Typography | L. Cook, M. Heighway, A. Eidam, E. Gunther, E. Bohn, N. Springer, G.Leuhof | Complete |
Tiger Team Process
1. Answer the call!
When a story moves from the backlog into the Discovery column on the DDS Kanban board, 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
AND
- have some time you can devote to the project (2-4 hours per week).
Once you express your interest, the Modus Product Manager will contact your manager to secure his/ her permission to divide your time between your team and the design system.
2. UX Board review of candidates
The board will review the volunteers to make sure the team has a good representation from different divisions, and it will choose a leader for the team.
3. Kick-off meeting
The Modus Product Manager will schedule an introductory kick-off meeting 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.
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 UX Board.
6. Feedback
The UX Board and 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.
7. Revisions and final approvals
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.
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.