> For the complete documentation index, see [llms.txt](https://tbw.rangle.io/the-better-way/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tbw.rangle.io/the-better-way/02-the-better-way/principle-five-integrate-governance/applying-the-principle-in-practice.md).

# Applying the principle in practice

To apply principle five in practice, start by targeting three key areas of focus.

The first focus area is *clarity*, which, as shown in Table V below, strives to ensure that both GRC managers and product teams understand the purpose of governance, risk and compliance and how to apply it appropriately within a technology powered, customer-first, product-centric, continuous delivery model.

![Table V: Understanding the role of governance vs risk vs compliance](/files/-Mdw_6PNy8AEuP2Fc7N5)

By creating this clarity, many organizations will be able to move away from a one-size-fits-all approach to GRC and use an evolutionary approach that is measured and rational. The key benefit of this approach is that when done well, lead times and time to value can dramatically improve.

The second focus area is *integration,* which attempts to solve the siloed, linear and niche-based approach to governance, risk and compliance by assembling long-lived, cross-functional GRC teams with the ability to continuously support product teams.

As shown in Figure I below, GRC teams are essentially coalitions of risk and compliance experts that work with product teams in a continuous review flow.

![Figure I: example of a GRC team and product team integration](/files/-Mdw_6POm_-LBVvaQxll)

The last focus area is *tooling*, which when applied appropriately, can significantly reduce manual effort and bureaucracy while also improving the overall alignment between disparate management levels within the organization. Getting the right tools in place can be incredibly helpful as it is often the case that disparate and unconnected tooling tends to pollute the organization and its functions with disconnected, duplicated and inaccurate data. But this can be solved through intelligent tooling, which enables organizations to connect their core tools and provide the business with a unified view of product value stream data and the associated risk and compliance data in a single, accurate and automated view. Learning to do this will of course take some time and effort. To get started, it may be helpful to review Dr. Mik Kersten’s book *Project to Product*.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://tbw.rangle.io/the-better-way/02-the-better-way/principle-five-integrate-governance/applying-the-principle-in-practice.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.