Jobs To Be Done

People across the IT lifecycle have various needs to drive projects/products forward.

This summarises those main jobs to be done and how AIM makes life easier.

Find and share models.

I want it to be easy to find and share Architecture models so that everyone in the business can understand:

  • How the business works.
  • How the IT platform supports the business.
  • What projects are planned and inflight.
  • What reusable components are available, and how do they work.


How to do this:

  • Load all of your project models into AIM
  • Extract content from project models that can serve as reusable design components.
  • Tag your models, so it’s easier to find them. For example, domain, sponsor, architect, risk level, etc.
  • Onboard your team and show them how to search in AIM, using the projects, components, and stories pages as well as project explorer, and component explorer. Also, show them how to surf through models to allow a better understanding of how the business and IT platform works.


Reuse architecture building blocks

I want to reuse Architecture building blocks in my designs to create project architectures more rapidly and of a higher quality.

I don’t want to waste time re-creating designs that already exist.


How to do this:

  • Create reusable component models by extracting elements from your project architecture models
  • Create stories for each component to explain how it works and how it can be consumed
  • From a project, select which components to reuse, and then import selected views from those components
  • Tailor your project architecture to suit by wiring up any imported components.


Create high-quality and consistent models

I want all Architecture models created to have some consistency, making it easier for people to review models.

I want any obvious technical modelling errors to be corrected.


How to do this:

  • Create Rules in AIM to validate models
  • Tag rules with what layer they apply to and what lifecycle stage they apply to so that Architects can use the appropriate rules.
  • Train the ArchiBot AI in AIM on your ‘good’ models so it can recommend model changes to help with model quality and consistency.


Make the most out of Architecture reviews.

I want Architecture models to be readily available to those who provide review feedback so that they can give feedback as the model evolves.

This is an alternative to feedback being provided too little or too late.


How to do this:

  • Create a Story for each project design decision.
  • Tag the story as ‘type: design decision’ so that others can locate these stories and provide feedback to you.


Understand what is planned and inflight

I want to see a complete list of Projects and Components so I can better plan and oversee the strategic investment.

A complete portfolio view, with the ability to group and filter, allows me to understand where there may be gaps and overlaps in the investment portfolio.


How to do this:

  • Make sure all your projects are loaded into AIM.
  • Give each project several tags to characterise it. For example, tags could include its investment status (Idea, Concept, Design, etc.), sponsor, risk, domain, and lead architect.
  • Use Project Explorer to group projects by their tags and drill into each project to ensure the appropriate architecture level has been defined per stage.


Create Diagrams for Documents

I want to create high-quality diagrams for architecture design documents or presentations easily.


How to do this:

  • Extract diagrams from AIM either by copying to the clipboard or downloading them as SVG
  • Paste or insert the diagram into your Word document, email, or presentation
  • Remember that you can also copy diagrams from stories if you want the diagram to have certain elements pre-highlighted


Avoid duplicate projects

I want to avoid duplicate projects being proposed and initiated.


How to do this:

  • Ensure that EA reference models are loaded into AIM and referenced when a new project is proposed.
  • Create projects in AIM for new project proposals and ensure that several key shaping inputs are provided, including the motivation layer (stakeholders, goals, drivers) and a story overlaid atop EA models (value chain, BCM) to indicate the initial scope of the project.
  • Analyse project proposals and merge or cull duplicate project proposals.


Manage technical debt

I want a way to manage technical debt which is tied to the Architecture


How to do this:

  • Create a story against each Component for each element of technical debt
  • Tag the story as ‘Type: Tech Debt’ 
  • Ensure the story elements are linked to those architectural elements which carry the technical debt.
  • Periodically review all technical debt stories by entering a filter on the Stories page.
  • Specifically invest to address technical debt, or encourage projects to address technical debt as they reuse and uplift components.