16 New KnowledgeHub Resources—and When to Reach for Each One

A process that nobody has mapped. A workshop that runs long and produces little. A problem that keeps getting solutions proposed before anyone agrees on what the problem really is. Most of these situations already have a technique designed for them. The challenge is knowing which one fits and having something ready to use when the moment arrives.

The latest batch of new KnowledgeHub resources (16 to be precise) is built around that gap. It covers two clusters: visual process modelling and diagramming on one side, and elicitation and problem-solving on the other.

Here’s what's new and how to put it to work.

Making Processes Visible

The Process Modelling insight lays the conceptual groundwork for this cluster: what process modelling is, when it adds value, and how to choose the right approach for the situation. It pairs with six ready-to-use diagramming templates: Activity Diagrams, Integrated DEFinition (IDEF), Use Case Diagrams, Value Stream Maps (2), Data Flow Diagrams, and State Diagrams.

Each template addresses a different modelling need.

• Activity Diagrams and Value Stream Maps are useful for visualizing workflow and identifying waste or handoff points
• Data Flow Diagrams track how information moves through a system
• Use Case Diagrams map relationships between users and system functions
• State Diagrams show how an object or system changes over time
• IDEF provides a structured decomposition format suited to complex operational processes 

Having all six in one place means less time setting up and more time modelling.

The Process Analysis insight and BPMN template extend the cluster further. Process Analysis covers how to evaluate an existing process for gaps, inefficiencies, and improvement opportunities, which is useful before a redesign effort or ahead of a requirements workshop. The BPMN template is provided here, though BPMN itself is also referenced in the Process Modelling insight, since it functions as a process diagram as well as an analysis tool. It provides a standardized notation format that works across teams and tools, reducing the back-and-forth that comes from everyone drawing processes differently.

Getting Better Information From People

Three new Workshop resources support the full arc of facilitated sessions: the Workshops insight covers how to plan and structure them, the Workshops example shows what a well-run session looks like in practice, and the Workshops checklist gives practitioners a concrete reference to work through before, during, and after. Used together, they make workshops considerably easier to prepare for and debrief.

The Interviews example complements the workshop set. Where workshops draw out group perspectives, interviews surface individual ones. And seeing a worked example of how interview findings are captured and used helps practitioners close the gap between a good conversation and useful documented output.

Collaborative Games rounds out the elicitation side. When standard techniques aren't generating the engagement or openness a session needs, structured games create the conditions for more honest and generative participation. The insight covers how to select and facilitate them without the session feeling forced.

Structuring Problem Investigation

Root Cause Analysis is the final addition and one of the most broadly applicable. It covers how to move from a symptom to a cause systematically, essential groundwork before requirements are written or solutions proposed. Teams that skip this step tend to build the right solution to the wrong problem. The insight provides the framework to avoid that.

How These Resources Fit Together

This batch covers a natural sequence in delivery work. A practitioner might open with Root Cause and Process Analysis to understand the problem, use Collaborative Games or Workshops to surface stakeholder perspectives, run Interviews to go deeper with key individuals, and then model the current and future state using the diagramming templates.

Each resource works independently, but the connections between them are worth knowing.

---

About the Author