{"id":707,"date":"2026-08-04T12:49:00","date_gmt":"2026-08-04T12:49:00","guid":{"rendered":"https:\/\/torreyowens.com\/staging\/?page_id=707"},"modified":"2026-08-04T22:17:25","modified_gmt":"2026-08-04T22:17:25","slug":"ticam","status":"publish","type":"page","link":"https:\/\/torreyowens.com\/staging\/ticam\/","title":{"rendered":"TICAM"},"content":{"rendered":"\n
\n
\"\"<\/figure>\n\n\n\n
\n
\n
\n

Defense<\/p>\n<\/div>\n\n\n\n

\n

Service Design<\/p>\n<\/div>\n\n\n\n

\n

Identity & Access<\/p>\n<\/div>\n<\/div>\n\n\n\n

Simplifying Tactical Identity Management<\/h3>\n\n\n\n

Designed identity lifecycle workflows that improved account provisioning, synchronization, and access management for disconnected military environments.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n
\n
\n

Overview<\/h2>\n<\/div>\n\n\n\n

What was this engagement?<\/p>\n<\/div>\n\n\n\n

TICAM (Tactical Identity, Credential & Access Management) was a service design initiative focused on understanding how identities were created, managed, and maintained across disconnected military environments. Rather than designing a new application, our team partnered with stakeholders across the Army to uncover operational challenges, map the identity lifecycle, and identify opportunities that would guide future capabilities.<\/p>\n\n\n\n

The outcome wasn\u2019t a single product. It was a shared understanding of the current state and a strategic roadmap for improving identity management across people, processes, and systems.<\/p>\n\n\n\n

\n
\n

I led the discovery and service design effort, partnering with Army stakeholders and cross-functional teams to understand the current state of tactical identity management and define a strategic direction for future capabilities.<\/p>\n\n\n\n

\n
\n

Role<\/p>\n\n\n\n

Senior Product & Service Designer<\/p>\n<\/div>\n\n\n\n

\n

Duration<\/strong><\/strong><\/strong><\/p>\n\n\n\n

6 mos<\/p>\n<\/div>\n\n\n\n

\n

Responsibilities<\/p>\n\n\n\n

Discovery \u2022 Service Design \u2022 Research \u2022 Journey Mapping \u2022
Service Blueprints \u2022 Workshop Facilitation \u2022 UX Strategy<\/p>\n<\/div>\n\n\n\n

\n

Collaborators<\/strong><\/p>\n\n\n\n

Product Management \u2022 Engineers \u2022 Army SMEs \u2022
System Administrators \u2022 Security Teams \u2022 UX<\/p>\n<\/div>\n\n\n\n

\n

Deliverables<\/strong><\/strong><\/strong><\/p>\n\n\n\n

Discovery Findings\u2022 Identity Lifecycle Maps \u2022 Service Blueprints \u2022 Capability Model \u2022 Opportunity Framework \u2022 Prioritized Roadmap \u2022 Future Experience Vision <\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n<\/div>\n<\/div>\n\n\n\n

\n
\n
\n
\n

The Challenge<\/h2>\n<\/div>\n\n\n\n

Why was this work needed?<\/p>\n<\/div>\n\n\n\n

Managing digital identities in military environments is far more complex than simply creating user accounts. A single service member may need access to dozens of applications, devices, networks, and mission systems throughout their career. Many of those systems were built independently, operated by different teams, and relied on manual processes to provision, update, or remove access.<\/p>\n\n\n\n

Over time, every organization developed its own way of managing identities. The result was a patchwork of disconnected workflows, inconsistent policies, and limited visibility across the identity lifecycle. Even experienced administrators often understood only the portion of the process they managed themselves.

Before a new solution could be designed, the team first needed a shared understanding of how identities actually moved through the organization from onboarding to off boarding<\/strong> and where those processes were breaking down.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\"\"<\/figure>\n\n\n\n\n\n
\n
\n
\n
\n

Discovery<\/h2>\n<\/div>\n\n\n\n

How did we understand it?<\/p>\n<\/div>\n\n\n\n

Before proposing solutions, we needed to understand how identity management actually worked across tactical environments\u2026 not how documentation said it worked.<\/p>\n\n\n\n

We met with Army operators, system administrators, support teams, and technical leaders<\/strong> to map the complete identity lifecycle, from onboarding through off boarding. Each conversation uncovered another piece of a much larger system, revealing how people, processes, and technologies intersected to support mission readiness.<\/p>\n\n\n\n


As workflows were mapped, patterns began to emerge. Teams were often solving the same problems in different ways, relying on manual coordination, institutional knowledge, and disconnected systems to accomplish critical tasks.<\/p>\n\n\n\n

Rather than validating assumptions, Discovery gave us a shared understanding of the current state and exposed the operational challenges that would shape every design decision moving forward.<\/p>\n<\/div>\n<\/div>\n\n\n\n

\"\"<\/figure>\n\n\n\n\n\n
\n
\n
\n
\n

What We Learned<\/h2>\n<\/div>\n\n\n\n

Patterns start to emerge.<\/p>\n<\/div>\n\n\n\n

The Discovery process uncovered recurring patterns across interviews, workflow analysis, and system documentation. Although each stakeholder experienced different parts of the identity lifecycle, the same operational challenges surfaced repeatedly.<\/p>\n\n\n\n

Rather than isolated technical issues, we found systemic problems that affected visibility, coordination, and mission readiness across the entire identity ecosystem.<\/p>\n\n\n\n

\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n\n\n
\n
\n
\n
\n

Framing<\/h2>\n<\/div>\n\n\n\n

Turning insight into a shared strategy.<\/p>\n<\/div>\n\n\n\n

Discovery gave us hundreds of observations from interviews, workflow mapping, and operational analysis. The next step was to transform those individual findings into a framework that could guide future decision-making.

We grouped recurring themes across the identity lifecycle, identified common capability gaps, and evaluated opportunities based on operational impact and technical feasibility. This shifted the conversation away from isolated issues and toward the underlying capabilities needed to improve identity management across tactical environments.

Rather than designing features, we designed a shared understanding. The resulting capability model provided a common language for Army stakeholders, engineers, and leadership to prioritize investments and align future work around the same operational goals.<\/p>\n\n\n\n

\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n\n\n
\n
\n
\n
\n

Identity Lifecycle<\/h2>\n<\/div>\n\n\n\n

A new way of understanding identity management.<\/p>\n<\/div>\n\n\n\n

As research progressed, a clear pattern emerged:

Identity problems were rarely isolated to a single system or task. Most access issues could be traced back to earlier decisions made during onboarding, provisioning, or account management.<\/mark><\/p>\n\n\n\n

Instead of viewing identity as a one-time event, we reframed it as a continuous lifecycle that spans onboarding, provisioning, access, maintenance, and off boarding. Every stage depends on the accuracy and consistency of the one before it.<\/p>\n\n\n\n

This lifecycle perspective exposed how fragmented systems, manual coordination, and disconnected environments introduced risk throughout the entire experience, not just at login. It also provided a shared mental model that helped stakeholders understand where improvements would have the greatest operational impact.

Viewing identity as a connected lifecycle revealed how decisions made at one stage influenced every stage that followed, creating a foundation for designing more resilient and scalable identity services.<\/em><\/p>\n\n\n\n

\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n\n\n
\n
\n
\n
\n

Capability Framework<\/strong><\/strong><\/h2>\n<\/div>\n\n\n\n

Defining what the future solution needed to enable.<\/p>\n<\/div>\n\n\n\n

Discovery and Framing revealed that improving identity management wasn\u2019t about replacing a single application. It required a coordinated set of capabilities that could support the entire identity lifecycle while reducing operational complexity.<\/p>\n\n\n\n

Rather than designing isolated features, we identified the core capabilities that would address recurring challenges across onboarding, provisioning, lifecycle management, and operational support<\/strong>. Each capability was grounded in validated research and aligned to real operational needs.<\/p>\n\n\n\n

Together, these capabilities established a strategic foundation for future product planning, helping stakeholders prioritize investments that would improve visibility, reduce manual effort, and create a more resilient identity ecosystem.

The capability model translated research into a practical roadmap, defining the foundational services needed to improve identity operations across people, processes, and systems.<\/em><\/p>\n\n\n\n

\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n\n\n
\n
\n
\n
\n

Constraints<\/strong><\/strong><\/h2>\n<\/div>\n\n\n\n

What this project reinforced.<\/p>\n<\/div>\n\n\n\n

TICAM reinforced that the most valuable design work often happens long before a screen is created.<\/p>\n\n\n\n

The biggest challenge wasn\u2019t designing a better interfaceit was helping stakeholders develop a shared understanding of a complex operational ecosystem. By listening to people across different roles, mapping their workflows, and synthesizing hundreds of observations, we uncovered patterns that no single team could see on its own.<\/p>\n\n\n\n


The experience also strengthened my appreciation for service design as a strategic discipline. When people, processes, and technology are viewed together rather than in isolation, opportunities emerge that extend far beyond individual features or applications.<\/p>\n\n\n\n

This project reminded me that the role of a designer isn\u2019t always to create the solution. Sometimes the greatest value comes from creating the clarity that allows the right solution to emerge.<\/p>\n\n\n\n

\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n\n\n
\n
\n
\n
\n

Outcome<\/strong><\/strong><\/h2>\n<\/div>\n\n\n\n

Creating a foundation for future capabilities.<\/p>\n<\/div>\n\n\n\n

By the end of the engagement, the team had transformed a collection of interviews, operational observations, and disconnected workflows into a shared understanding of tactical identity management.<\/p>\n\n\n\n

The discovery, framing, and service design artifacts provided stakeholders with a common language for discussing identity challenges, evaluating opportunities, and prioritizing future investments. Rather than relying on assumptions or isolated perspectives, decisions could now be grounded in validated research and a holistic view of the identity lifecycle.<\/p>\n\n\n\n

Although the project was not focused on delivering a production application, it established the strategic direction for future capabilities. The work aligned technical teams, product leadership, and Army stakeholders around a common vision for improving identity management across tactical environments.

The outcome was more than a collection of research artifacts. It was a strategic framework that enabled future planning, aligned stakeholders, and established a shared vision for modernizing tactical identity management.<\/em><\/p>\n\n\n\n

\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n\n\n
\n
\n
\n
\n

Reflection<\/strong><\/strong><\/h2>\n<\/div>\n\n\n\n

What this project reinforced.<\/p>\n<\/div>\n\n\n\n

TICAM reinforced that the most valuable design work often happens long before a screen is created.<\/p>\n\n\n\n

The biggest challenge wasn\u2019t designing a better interface, it was helping stakeholders develop a shared understanding of a complex operational ecosystem. By listening to people across different roles, mapping their workflows, and synthesizing hundreds of observations, we uncovered patterns that no single team could see on its own.<\/p>\n\n\n\n


The experience also strengthened my appreciation for service design as a strategic discipline. When people, processes, and technology are viewed together rather than in isolation, opportunities emerge that extend far beyond individual features or applications.<\/p>\n\n\n\n

This project reminded me that the role of a designer isn\u2019t always to create the solution. Sometimes the greatest value comes from creating the clarity that allows the right solution to emerge.<\/p>\n\n\n\n

Success wasn\u2019t measured by the number of screens we designed. It was measured by how clearly we helped others understand the problem before deciding how to solve it.<\/strong><\/p>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n
\n

Have a complex problem to solve?<\/h2>\n\n\n\n

I\u2019m always interested in thoughtful conversations about product design, service design, enterprise systems, and human-centered AI.<\/p>\n\n\n\n

\n
Let\u2019s Connect!<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/body>","protected":false},"excerpt":{"rendered":"

Defense Service Design Identity & Access Simplifying Tactical Identity Management Designed identity lifecycle workflows that improved account provisioning, synchronization, and access management for disconnected military environments. Overview What was this engagement? TICAM (Tactical Identity, Credential & Access Management) was a service design initiative focused on understanding how identities were created, managed, and maintained across disconnected […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"om_disable_all_campaigns":false,"pagelayer_contact_templates":[],"_pagelayer_content":"","footnotes":""},"class_list":["post-707","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/torreyowens.com\/staging\/wp-json\/wp\/v2\/pages\/707","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/torreyowens.com\/staging\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/torreyowens.com\/staging\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/torreyowens.com\/staging\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/torreyowens.com\/staging\/wp-json\/wp\/v2\/comments?post=707"}],"version-history":[{"count":5,"href":"https:\/\/torreyowens.com\/staging\/wp-json\/wp\/v2\/pages\/707\/revisions"}],"predecessor-version":[{"id":753,"href":"https:\/\/torreyowens.com\/staging\/wp-json\/wp\/v2\/pages\/707\/revisions\/753"}],"wp:attachment":[{"href":"https:\/\/torreyowens.com\/staging\/wp-json\/wp\/v2\/media?parent=707"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}