Skip to content

Commit 9b639f5

Browse files
committed
docs(homepage): redesign homepage and intro page with marketing-focused content
- Rewrite homepage (docs/index.md) with hero section, benefit cards, and clear CTAs - Rewrite intro page (docs/intro/index.md) with concise, scannable content - Remove embedded objectives cards from both pages (objectives have dedicated page) - Fix broken link (concept/index.md -> concept/use-case-tree.md) - Fix grammar: 'Learn the Use Case Tree' -> 'Explore the Use Case Tree' - Fix list formatting in docs/objective/modularity.md
1 parent e353720 commit 9b639f5

File tree

3 files changed

+122
-76
lines changed

3 files changed

+122
-76
lines changed

docs/index.md

Lines changed: 68 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,9 @@
11
---
22
description: >-
3-
Learn the Use Case Tree Method for developing Enterprise Knowledge Graphs.
4-
A comprehensive, proven methodology to build business capabilities through
5-
structured use cases, outcomes, and workflows.
3+
Build an Enterprise Knowledge Graph that delivers business value—
4+
one use case at a time. Explore the Use Case Tree Method: a proven,
5+
business-owned approach to plan, scope, and deliver reusable
6+
capabilities.
67
date_published: "2022-01-01"
78
keywords:
89
- EKG method
@@ -16,10 +17,68 @@ hide:
1617
- toc
1718
---
1819

19-
# Use Case Tree Method for Business Capabilities
20+
# Use Case Tree Method
2021

21-
{%
22-
include-markdown "objective/index.md"
23-
start="<!--objectives-index-start-->"
24-
end="<!--objectives-index-end-->"
25-
%}
22+
Build an _Enterprise Knowledge Graph (EKG)_ that delivers business value—
23+
**one use case at a time**.
24+
25+
[Get started](intro/index.md){ .md-button .md-button--primary }
26+
[Explore the Use Case Tree](concept/use-case-tree.md){ .md-button }
27+
[Browse example use cases](https://catalog.ekgf.org/){ .md-button }
28+
29+
<div class="grid cards" markdown>
30+
31+
- __Business-owned roadmap__
32+
33+
Align strategy → capabilities → delivery with one shared artifact.
34+
35+
- __Composable delivery__
36+
37+
Ship small, reusable building blocks instead of monolithic systems.
38+
39+
- __Quality + compliance__
40+
41+
Make traceability, controls, and auditability part of the design.
42+
43+
- __Production-proven__
44+
45+
A method refined across real EKG use cases running in production.
46+
47+
</div>
48+
49+
## What is the Use Case Tree?
50+
51+
The [Use Case Tree](concept/use-case-tree.md) is a high-level map of the
52+
capabilities your enterprise plans to build—broken down into use cases with
53+
dependencies, so you can deliver in the right order.
54+
55+
## What you’ll learn on this site
56+
57+
<div class="grid cards" markdown>
58+
59+
- __Introduction__
60+
61+
What the method is, who it’s for, and how it creates leverage.
62+
63+
[:octicons-arrow-right-24: Read the introduction](intro/index.md)
64+
65+
- __Objectives__
66+
67+
Why the method works: interoperability, reuse, modularity, quality,
68+
alignment, and more.
69+
70+
[:octicons-arrow-right-24: Explore the objectives](objective/index.md)
71+
72+
- __Concepts__
73+
74+
The core building blocks: use case, outcome, workflow, terms, and more.
75+
76+
[:octicons-arrow-right-24: Explore concepts](concept/use-case.md)
77+
78+
- __Process__
79+
80+
Plan, build, and run EKG components—from first use case to scale.
81+
82+
[:octicons-arrow-right-24: Explore the process](process/index.md)
83+
84+
</div>

docs/intro/index.md

Lines changed: 52 additions & 65 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,9 @@ hide:
55
- toc
66
- navigation
77
description: >-
8-
Introduction to the Use Case Tree Method for developing Enterprise Knowledge
9-
Graphs. Learn how this method enables strategic use cases, data quality,
10-
compliance, and competitive advantage.
8+
A practical introduction to the Use Case Tree Method: a business-owned
9+
way to build Enterprise Knowledge Graph capabilities with modular
10+
delivery, reuse, and governance by design.
1111
keywords:
1212
- use case tree method
1313
- EKG introduction
@@ -19,70 +19,57 @@ schema_type: "Article"
1919

2020
# Use Case Tree Method for Business Capabilities
2121

22-
Your enterprise embarked upon a strategic innovative journey towards
23-
establishing a full scale _Enterprise Knowledge Graph (EKG)_ in order
24-
to be able to:
25-
26-
1. implement use cases that enable more foundational data quality
27-
for your enterprise’s business processes,
28-
2. be more easily compliant with regulations and
29-
3. enable strategic use cases that create a competitive advantage.
30-
4. To connect business silos to make them work together
31-
5. To create business agility by creating reusable business components
32-
6. To capture intellectual property and manage your business value
33-
34-
The key _artifact_ in the development of an EKG is "the [Use Case Tree](../concept/use-case-tree.md)":
35-
36-
- The [Use Case Tree](../concept/use-case-tree.md) provides a
37-
**long term data strategy and business capability plan**.
38-
39-
- The [Use Case Tree](../concept/use-case-tree.md) is the
40-
**high-level requirements overview, scoping and dependency model**.
41-
<br/>It gives a _mile wide, inch deep_ view of business capabilities.
42-
43-
Traditionally, data strategy, architecture and models i.e.
44-
_specifications of business requirements_ on one side and technology
45-
and software, i.e. _functionality_ on the other side, are separate.
46-
They are concerns of different departments; different groups of
47-
specialists think about these concepts in their own way and have their
48-
own practices and models for it.
49-
For any given development of a business capability that is supported
50-
by technology, different groups of people, often across many departments, will get involved and they all
51-
have their own way of looking at it.
52-
There is no shared language, not one single artifact that they can
53-
all talk to and reason about.
54-
The [Use Case Tree](../concept/use-case-tree.md) is that single artifact.
55-
It provides one single construct, owned by _the business_, and
56-
primarily driven by business strategy, that every group of people,
57-
every specialist, can relate their way of thinking to.
58-
This includes not only data and technology specialists but also project
59-
managers, financial managers, security and compliance officers,
60-
operations engineers and so forth.
61-
All their models and different ways of looking at a given capability
62-
can be plugged into the [Use Case Tree](../concept/use-case-tree.md) as different views.
63-
64-
Everything we ever do in an organization, especially in the data and
65-
technology pillars of that enterprise, should be related to at least
66-
one use case in the organization's [Use Case Tree](../concept/use-case-tree.md).
67-
68-
The [Use Case Tree](../concept/use-case-tree.md) is a breakdown of strategic planned-for
69-
capabilities into smaller building blocks, all called use cases.
70-
Strategic long term use cases such as
71-
_[Enterprise Risk Management](https://catalog.ekgf.org/use-case/risk-management/)_
72-
or _[Client 360](https://catalog.ekgf.org/use-case/client-360/)_ are
73-
down into smaller use cases that can---and should---be done first.
22+
Turn strategy into reusable EKG components—without boiling the ocean.
23+
24+
[Explore the Use Case Tree](../concept/use-case-tree.md){ .md-button .md-button--primary }
25+
[Explore objectives](../objective/index.md){ .md-button }
26+
[Browse example use cases](https://catalog.ekgf.org/){ .md-button }
27+
28+
<div class="grid cards" markdown>
29+
30+
- __What you get__
31+
32+
A single business-owned artifact that aligns strategy, data, and delivery.
33+
34+
- __How you deliver__
35+
36+
Build small use cases first, then compose them into bigger capabilities.
37+
38+
- __How you scale__
39+
40+
Reuse knowledge safely with governance and traceability by design.
41+
42+
</div>
43+
44+
## The Use Case Tree in one sentence
7445

75-
Each use case is a module---an EKG-component so you will---a
76-
building block with which other use cases can be constructed
77-
(see ["Modularity Managed"](../objective/modularity.md)).
46+
The [Use Case Tree](../concept/use-case-tree.md) is the map of the capabilities
47+
your enterprise plans to build—broken down into use cases with dependencies,
48+
so you can deliver in the right order.
49+
50+
## Why this works (objectives)
51+
52+
This method is designed to help you achieve outcomes like:
53+
54+
- **Interoperability** across domains and teams
55+
- **Modularity + reuse** (composable business capabilities)
56+
- **Captured requirements and knowledge** as durable assets
57+
- **Increased quality** through structure and traceability
58+
- **Alignment with business strategy** and managed expectations
59+
60+
[:octicons-arrow-right-24: Explore all objectives](../objective/index.md)
61+
62+
## Start small, compose big
63+
64+
Strategic capabilities like
65+
_[Enterprise Risk Management](https://catalog.ekgf.org/use-case/risk-management/)_
66+
or _[Client 360](https://catalog.ekgf.org/use-case/client-360/)_ are broken down
67+
into smaller use cases that you can—and should—deliver first.
7868

79-
The Use Case Tree Method is a practice that has been developed and
80-
used for many EKG use cases that are running in production.
69+
Each use case is a reusable building block (see
70+
["Modularity Managed"](../objective/modularity.md)).
8171

82-
{%
83-
include-markdown "../objective/index.md"
84-
start="<!--objectives-index-start-->"
85-
end="<!--objectives-index-end-->"
86-
%}
72+
The Use Case Tree Method has been developed and applied in EKG use cases that
73+
are running in production.
8774

8875

docs/objective/modularity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -153,8 +153,8 @@ composable businesses.
153153
- [Oxford Global Projects Academy - Smart Scaling: Modularity & Speed](https://academy.oxfordglobalprojects.com/pages/smart-scaling)
154154
- [Flyvbjerg, Bent, Harvard Business Review - Make Megaprojects More Modular](https://hbr.org/2021/11/make-megaprojects-more-modular)
155155
- [Flyvbjerg, Bent, Make Megaprojects More Modular (October 19, 2021). Harvard Business Review, 2021, November-December Issue, pp. 58-63.](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3937465)
156-
- [Flyvbjerg, Bent, What Is Negative Learning — and Positive?](https://medium.com/geekculture/what-is-negative-learning-and-how-to-avoid-it-452d9e4c8263)-
157-
[Gartner Keynote: The Future of Business Is Composable](https://www.gartner.com/smarterwithgartner/gartner-keynote-the-future-of-business-is-composable)
156+
- [Flyvbjerg, Bent, What Is Negative Learning — and Positive?](https://medium.com/geekculture/what-is-negative-learning-and-how-to-avoid-it-452d9e4c8263)
157+
- [Gartner Keynote: The Future of Business Is Composable](https://www.gartner.com/smarterwithgartner/gartner-keynote-the-future-of-business-is-composable)
158158
- [Walkme - Packaged Business Capabilities (PBCs)](https://www.walkme.com/glossary/packaged-business-capabilities/)
159159
- [ElasticPath - What are Packaged Business Capabilities?](https://www.elasticpath.com/blog/what-are-packaged-business-capablities)
160160
- [Venture Leap - The future is called _“Packaged Business Capabilities”_](https://venture-leap.com/en/the-leap/the-future-is-called-packaged-business-capabilities-2/)

0 commit comments

Comments
 (0)