Skip to content

The organizational model

Your organization, as one model.

Products, projects, people, knowledge, infrastructure and risks, connected. See what a change will touch before it lands.

Interactive preview · sample data8 layers · 40 nodes · 58 relationships
PeopleKnowledgeInfrastructureSoftwareProductsProjectsTasksRisksBilling EngineerCTOHead of ProductPlatform LeadSecurity LeadCEOBilling rulesRecovery planIncident runbookAudit evidenceDatabase serversData centerCore networkCloud regionCard processorBilling engineFraud scoringPublic APICore platformMobile backendMerchant PortalCheckoutPartner APIMobile WalletBilling rewriteCloud migrationPartner API v2Vendor reviewWallet launchMap rulesBuild invoicingParallel runMove ledgerSpec API v2Vendor sign-offLoad testKey-person riskAging serversSingle regionReview backlog
Select any node to trace its connections. Open it, or double-click, to go one level deeper.

The problem

Every tool is right about its slice. None of them know how the slices connect.

So the real questions (what does this change touch, who is holding this up, what did we plan) are answered by hand, in a meeting, from stale slides.

TrackerWikiSpreadsheetRepositoryCloud consoleRisk registerRoadmap deckOrg chartMonitoringNine tools, no shared picture

Ask the question you cannot answer today

Five questions. One model answers all of them.

Interactive preview · sample dataCEO
PeopleKnowledgeInfrastructureSoftwareProductsProjectsTasksRisksBilling EngineerCTOHead of ProductPlatform LeadSecurity LeadCEOBilling rulesRecovery planIncident runbookAudit evidenceDatabase serversData centerCore networkCloud regionCard processorBilling engineFraud scoringPublic APICore platformMobile backendMerchant PortalCheckoutPartner APIMobile WalletBilling rewriteCloud migrationPartner API v2Vendor reviewWallet launchMap rulesBuild invoicingParallel runMove ledgerSpec API v2Vendor sign-offLoad testKey-person riskAging serversSingle regionReview backlog

Step 1 of 4 · The signalThe Mobile Wallet launch in two new countries is three weeks behind. The product is flagged and the plan says so.

TodayAsk three people, open the tracker, a spreadsheet and last week's slides.
With OmniVIEWSelect the product and follow what it waits on.

Previews run on an invented company with sample data.

One model, every job

The same node, in the view that fits the work.

Each role gets a workspace built for its job. Underneath, they read and write one model, so they cannot disagree.

Products

Stage, health and delivery of every product.

  • ProductStageDelivery
  • Merchant PortalScaling47%
  • CheckoutMature82%
  • Mobile WalletLaunching58%
  • Partner APIBeta36%

Same node, different view. The Merchant Portal in the graph, the plan and the risk register. Preview with sample data.

The fourth dimension

Drag to last quarter. Drag to next.

A status slide is stale the day it is written. The model keeps what existed and what is planned, so the same question works on any date.

Interactive preview · sample dataNow
PeopleKnowledgeInfrastructureSoftwareProductsProjectsTasksRisksBilling EngineerCTOHead of ProductPlatform LeadSecurity LeadCEOBilling rulesRecovery planIncident runbookAudit evidenceDatabase serversData centerCore networkCloud regionCard processorBilling engineFraud scoringPublic APICore platformMobile backendMerchant PortalCheckoutPartner APIMobile WalletBilling rewriteCloud migrationPartner API v2Vendor reviewWallet launchMap rulesBuild invoicingParallel runMove ledgerSpec API v2Vendor sign-offLoad testKey-person riskAging serversSingle regionReview backlog

NowNothing here is only planned. Everything shown exists.

Why it is different

Not another place to track work.

  • Task trackers know the work.Not the systems it runs on, or the people it depends on.
  • Wikis know the words.Not which of them are out of date, or what they describe.
  • CMDBs know the machines.Not the products that would stop if one failed.
  • Dashboards know the numbers.Not the relationships behind them, or last quarter's.
  • OmniVIEW knows how they relate.And lets every one of those tools keep doing what it does best.

Capabilities

Everything about your organization, in one place.

One connected model

  • Layered graph in 3D and 2DLayers as planes, nodes as cards
  • Drill into any nodeFrom the organization down to a single component
  • Impact and structure lenses
  • Templates for any kind of organization

Time

  • Any date, past or plannedScrub the whole organization through time
  • Planned versus actual, side by side
  • Every change recorded and attributed

Planning and delivery

  • Work breakdown and GanttDependencies and the critical path included
  • Boards, lists and roadmaps
  • Capacity and resource planning

The whole organization

  • Products, architecture and infrastructure
  • Knowledge, people and skills
  • Risks with owners and mitigations

Always current

  • Connects to your toolsTrackers, wikis, repositories, cloud, monitoring
  • Imports from spreadsheets and webhooks
  • Freshness signals on everything

Ready for the enterprise

  • Roles and permissions per graph
  • Single sign-on and provisioning
  • Audit trail and data residency

Connect, do not replace

Your tools stay in charge of their domains.

Issue trackers
Wikis and documents
Source control
Cloud platforms
Monitoring
Spreadsheets and CSV
Webhooks and APIs

Code, pipelines and tickets do not move.Only the relationships between them are recorded. Every change is logged and attributed, and imports update what is there instead of duplicating it.

Intelligence

An organization you can ask.

Ask a question in plain language. The answer is traced through the model, so you can see why, and open whatever sits behind it.

Ask

In your own words

  • Which launches depend on a single approver?
  • What changes if we leave this data center?
  • Who else knows this system?

Understand

With the reasoning shown

  • Every answer traced across the layers it touched
  • Impact explained, not just listed
  • Stale or contradictory data called out

Act

From the same place

  • Open the plan, the owner or the risk behind any answer
  • Compare what was planned with what happened
  • Share a view with the people who decide

Previews on this page use a fictional company and sample data.

Start small

Start with one question.