Learn

👨‍🏫 Information Architecture (IA) for TPM’s

Understanding effective Information Architecture can elevate you from a good Technical Program Manager to a High-Impact one. 

Let’s dive in.

More than a status report.

I’m preaching to the choir here but…

Technical Program Managers are a whole lot more than status updaters and report writers.

A senior engineering manager once told me…

He saw TPMs as excessive overhead, merely bugging people for status updates and writing generic reports. However, after a year working together, he acknowledged the undeniable value of TPMs in large-scale execution, even crediting our success to TPM engagement.

(Shout out to my fellow talented TPMs at HashiCorp!)

As a Technical Program Manager (TPM), you might often feel like your role is perceived as reduced to just sending out status updates. It's a common frustration, and it can make your work seem mundane and disconnected from the bigger picture.

Again, preaching to the choir, but status reporting is the tip of the iceberg. So what is the rest of the iceberg that supports high quality status reporting?

Say hello to Information Architecture.

Information Architecture (IA) Fundamentals

Hopefully, you now identify as an Information Architect, as it's a big part of your job. TPMs manage one or multiple programs, generating internal information on the regular! TPMs are often the “glue” of large-scale initiatives, and Information Architecture practices make this visible and practical.

Let’s explore IA fundamentals applicable to better program execution.

What is “good” IA?

Effective Information Architecture has several common characteristics:

• Clarity: The structure and labeling of information are clear and understandable.

• Efficiency: Information is organized to minimize the time and effort required to complete tasks.

• Usability: The system is intuitive and user-friendly.

• Consistency: Uniform experience across different sections enhances efficiency.

• Flexibility: The IA can adapt to changes and growth over time.

Use these attributes to evaluate how you’ve organized your program information.

Core Components of IA

How do we achieve effective IA? IA is a well-researched field with established principles. This means we have some first-principles to build on.

• Organization Systems: Define how information is structured. Common patterns include:

  • Hierarchical: Tree-like structure with parent-child relationships (e.g., website navigation menus).

  • Sequential: Information in a specific order (e.g., instruction manuals).

  • Matrix: Grid format allowing users to choose their view (e.g., comparison tables).

• Labeling Systems: Terminology used to describe and categorize information.

• Navigation Systems: How users browse or move through information, often influenced by the design of tools like Confluence and Jira.

• Search Systems: Enable users to look for information using keywords or phrases.

The most applicable IA components for TPM’s are organizational systems and labeling. We will focus on these two for the rest of this article.

Applying IA to your job as a TPM

There are countless ways to apply IA principles to your job as a TPM. Here are some potential use cases:

Use Case 1: General Program Structure with a Hierarchical Organizational Pattern

Program Structure should, by default, utilize the hierarchical organizational pattern. This won’t surprise many of you, but perhaps put words to the natural way we want to organize things.

Why is it “good” IA? This structure a big win on two of the (1) clarity and (2) efficiency.

Use Case 2: Scalable Program Onboarding with a Sequential Organizational System

Programs often start with a core group of stakeholders but may grow as they progress. For scalable onboarding, use a Sequential Organizational System.

If you’ve got teams or stakeholders to onboard to your program somewhat regularly, do it in a scalable way by utilizing a Sequential Organizational System.

What does this look like? Define the starting point, build up logical context, and walk them through how their slice of the pie fits in.

Use Case 3: Crisp Risk Management with a Matrix Organizational System

Managing risk is central to your job as a TPM. Risks have many facets, and using a matrix organizational system to display and discuss them allows for informed decisions.

By using a matrix organizational system to display and discuss risks, you can take in these many facets and make informed decisions.

What does this look like? An interactive risk log where users can manipulate data by priority, severity, impact, dates, owning team, etc.

Use Case 4: Jira Data Categorization with a Labeling System

Jira is the data store for program execution. Keeping data clean and consistent is crucial for insight into execution health.

Using a labeling system to categorize Jira data allows for easier automation and visualization, helping your team stay aligned and reach objectives more effectively.

TPM’s are Information Architects.

Whether you realized it or not, you are doing a ton of information architecture. It certainly helped me to understand that there is a whole field of study dedicated to the effective organization of information for more effective interaction with it.

Now go forth, TPM’s, and architect your information!

People

🤝 Want to help your fellow TPM’s? 2-3 minutes for a newsletter testimonial?

Okay, here’s the deal. This newsletter has received more traction than I expected. We just crossed 1000 active subscribers! 

I plan to keep writing and keep growing this newsletter to better connect the TPM community. In the future, I want to make interactions among fellow subscribers more active.

I don’t ask much of you, this is a free newsletter. So I’m asking you take 1-2 minutes to help me: provide a written testimonial (even if its anonymous).

How will this be used? I want to upgrade the sign-up page of The TPM Craft Newsletter. Testimonials serve as very valuable social proof that this free newsletter is pretty decent.

Please? 😁 

Resources

📚 The Phoenix Project

I’ll be honest. Today’s resource doesn’t have a special discount or anything. It’s just a good book.

Unlike most books we read to level up our skills, this one takes the form of a novel. The story line is all too relatable.