02 / The capability indexDune Ridge / Technology

Find the right
point of entry.

An information challenge rarely sits inside one screen. These four areas offer different ways to examine the same connected environment.

01Content systemsA structure for the information you publish.Model / Publish / Maintain02Search & discoveryHelp people find the right information, in their own terms.Find / Filter / Understand03Knowledge workspacesUseful references, with ownership and context attached.Collect / Review / Reuse04System connectionsMove structured information without losing its meaning.Map / Connect / Observe
Selecting a starting point

Follow the friction.

If the same facts need repeated correction, begin with content systems. If useful material exists but people cannot find it, look at search and discovery. If a team needs a reliable place to consult guidance, consider a knowledge workspace. If information diverges across tools, examine the connections.

These distinctions help frame the conversation. They do not require separate projects. A resource collection may need a small content model, a better discovery interface, and one carefully scoped connection. The proposal should explain which parts belong together and which can wait.

We prefer a starting point that can be described and reviewed: a representative content set, a group of priority queries, a single publishing workflow, or a defined system boundary.

A practical scope conversation

What can the first delivery clarify?

The current environment

Identify the sources, platforms, permissions, and responsibilities already in place. Existing constraints are part of the design brief, not an afterthought.

The intended use

Describe the people using the information and the task that should become easier. Concrete examples are more useful than a long list of desired features.

The reviewable result

Agree on what will be delivered and how it will be assessed. Documentation, demonstrations, and known limitations should be part of that agreement.

Platform selection, migration volume, integrations, access controls, and ongoing support depend on the agreed project. This website describes areas for discussion rather than a fixed package or guaranteed outcome.

Explore working together