Your workspace scores 75/100 Established

Your workspace scores 75/100, placing it in the Established range. System Maturity stands out at 97 -- with 412 relational connections and core systems like Tasks, Companies, Exec_Contacts forming a coherent operational backbone. Content Health at 53 represents the greatest opportunity for improvement. Strengthening content health across your 10 core systems would have the single largest impact on overall workspace health.

Gravity Map

Your workspace is anchored by 10 core systems -- Tasks, Companies, Exec_Contacts and 1 more -- which together account for 34% of all workspace content and are connected through 72 relational links. These are the operational backbone of your team's work in Notion. 154 supporting databases feed these core systems, while 249 peripheral databases handle secondary functions.

Show Connections

Tasks

100
4,814 entries37 props7 relations2 unused1 low util
Supporting (1)

Companies

98
272 entries83 props20 relations13 unused14 low util
Supporting (7)

Exec_Contacts

98
1,060 entries26 props9 relations8 unused8 low util
Supporting (1)

Projects

94
129 entries33 props18 relations1 unused8 low util
Supporting (9)+1 more

Client Opportunities

92
152 entries42 props9 relations6 unused8 low util
Supporting (2)

Meetings

91
1,236 entries14 props6 relations1 unused1 low util
Supporting (2)

Draft Contracts

84
168 entries23 props3 relations1 low util

Projects

83
10 entries20 props6 relations3 unused
Supporting (5)

Internal Docs

79
517 entries13 props5 relations
Supporting (2)

iProjects

79
28 entries15 props6 relations2 low util
Supporting (4)
10 core155 supporting248 peripheral
View full ERD →

Team Engagement

Workspace activity is driven primarily by 30 of your 32 team members, who account for the majority of page edits. This creates knowledge concentration risk -- 2 core systems including Draft Contracts, Projects are maintained primarily by one person each. Distributing ownership of these critical systems through documentation handoffs and shared responsibilities would significantly improve team resilience.

Edit Distribution

Bryan (NS) (53%)
Josh Redd (28%)
Eva Živanovič (8%)
Cherihan (5%)
Madison Payton (2%)
Notion State (1%)
UserCreatedEditedActivityLast Active
Bryan (NS)1116110578powerFeb 15
Josh Redd56415613powerFeb 10
Eva Živanovič17561657powerFeb 16
Cherihan822937powerFeb 16
Madison Payton344412powerFeb 6
Notion State156148dormantDec 8
Toni Sian120130activeFeb 16
Yina (NS)181102activeFeb 13
Ahnaf (NS)3480activeFeb 16
Cynthia Njuguna3946activeFeb 11
Zacharias Cicek639occasionalJan 26
Bayler1436activeFeb 9
Conor Edwards027inactiveSep 11
Sal Asta018occasionalFeb 6
Leslie Clark07activeFeb 16

Content Health

After accounting for 110 reference databases where infrequent editing is expected, 186 operational systems appear to have gone dormant -- including iProjects that your team depends on as core system. This represents digital debt that can erode trust in Notion as a reliable source of truth. A quarterly content review targeting stale operational databases keeps your workspace lean and trustworthy.

5,326 standalone pages189 active, 308 warning, 3434 stale, 1395 abandoned
4%fresh
Fresh: 189
Warning: 308
Stale: 3434
Abandoned: 1395
TasksEisenhower MatrixJosh ReddJun 121732d
QuartersOKR ForgeJosh ReddJun 111732d
Key ResultsOKR ForgeJosh ReddJun 111732d
ObjectivesOKR ForgeJosh ReddJun 111732d
CoffeesJosh ReddJun 121732d
Tasting NotesJosh ReddJun 121732d
Time BlockTime BlockingJosh ReddJun 151728d
- StrikeTaskJosh ReddSep 151271d
- TagsJosh ReddOct 61250d
- ProjectsJosh ReddOct 61250d
TJC HQClient Pack Template (TJC)Josh ReddMar 311074d
Executive DataClient Pack Template (TJC)Josh ReddMar 311074d
Executive HQClient Pack Template (TJC)Josh ReddMar 311074d
Notion Ops HQClient Pack Template (TJC)Josh ReddMar 311074d
ChecklistClient Pack Template (TJC)Josh ReddMar 311074d
Annual Client StrategyTJC HQJosh ReddMar 311074d
The TeamExecutive HQJosh ReddMar 311074d
Message from the FounderExecutive HQJosh ReddMar 311074d
About our TeamExecutive HQJosh ReddMar 311074d
TJC DATAJosh ReddMar 311074d
TJC Notion TutorialsJosh ReddMar 311074d
Company ScorecardJosh ReddMar 311074d
Team WikiJosh ReddMar 311074d
About UsJosh ReddMar 311074d
Tasting House OS PackJosh ReddMar 311074d
TJC OS PackJosh ReddMar 311074d
Finder PackJosh ReddMar 311074d
Project Manager PackJosh ReddMar 311074d
X ProjectsJosh ReddMar 311074d
X ContactsJosh ReddMar 311074d
X MonthsJosh ReddMar 311074d
X TasksJosh ReddMar 311074d
X ClientsJosh ReddMar 311074d
X Pitch IdeasJosh ReddMar 311074d
X ResourcesJosh ReddMar 311074d
Devinne OSJosh ReddMar 311074d
X TeamsJosh ReddMar 311074d
X NotesJosh ReddMar 311074d
Perspectives Task Manager (Basic) PackPerspectives Task ManagerJosh ReddMay 301014d
Perspectives Task Manager (Basic) PackPerspectives Task ManagerJosh ReddMay 301014d
- NotesJosh ReddJun 31010d
StrikeStudent Pro PackJosh ReddJun 131000d
Pack_OSJosh ReddJul 18965d
Pack_MeOSJosh ReddJul 18965d
Pack_Company OSJosh ReddJul 27956d
Pack_FinderJosh ReddAug 8944d
Pack_Project ManagerJosh ReddAug 8944d
Pack_Spark ManagerJosh ReddAug 8944d
T-ProjectsBryan (NS)Oct 24867d
T-Key ResultsBryan (NS)Oct 24867d

Architecture

Your workspace has 412 relational connections organizing 304 databases into an interconnected system. Services - For Proposals serves as the central hub with 35 connections, anchoring your workspace architecture. 109 databases operate without relational connections -- identifying natural integration points would further strengthen the system.

View full ERD →

Recommendations

We've identified 10 improvement opportunities, 6 of which directly affect your core operational systems. 3 quick wins -- including connect 5 active orphan databases -- could improve your workspace maturity score by an estimated 10 points. 7 larger efforts targeting team engagement and system architecture would drive the most significant long-term improvement.

high+12 pts

Redistribute workspace ownership through documentation and training

Current Gini coefficient of 0.91 indicates concentrated editing. Implement documentation handoffs, shared responsibilities for core systems, and regular workspace orientation sessions for the team.

Builds institutional knowledge across the team, reducing key-person risk and improving resilience.

Pillar: engagementAffects: core systems
high+8 pts

Cross-train team members on 98 critical databases

Establish backup maintainers for databases with single-contributor dependency: Draft Contracts (currently 88% by Bryan (NS)); Projects (currently 90% by Bryan (NS)); v3__Tasks (currently 98% by Unknown).

Eliminates single points of failure on critical operational systems.

Pillar: engagementAffects: core systems
high+7 pts

Audit and reactivate 91 stale workflow databases

Determine if stale workflow databases represent active processes or should be archived. Priority: iProjects (core), PortCo Projects (peripheral), v1_Projects (peripheral).

Ensures workflow databases reflect actual team processes and removes confusion about which systems are authoritative.

Pillar: content_healthAffects: core systems
medium+6 pts

Integrate 1 high-activity isolated databases

Design relational connections for databases with high activity but no relations: Tasks Tracker. These contain valuable data that could be cross-referenced with core systems.

Transforms isolated data stores into interconnected systems, enabling rollups and navigation.

Pillar: architectureAffects: core systems
medium+3 pts

Connect 5 active orphan databases

Create relation properties to link active but unconnected databases to core systems: Link "Tasks Tracker" to "Tasks" via a relation property; Link "Exec_Docs" to "Tasks" via a relation property; Link "NS Help Library" to "Tasks" via a relation property.

Increases workspace coherence and enables cross-referencing between related data.

Pillar: architectureAffects: supporting systems
medium+10 pts

Implement database creation and maintenance governance

Establish guidelines for when to create new databases versus extending existing ones. Include naming conventions, required properties, and a review cadence for unused databases.

Prevents workspace sprawl and ensures new databases integrate into the existing system architecture.

Pillar: architectureAffects: peripheral systems
medium+5 pts

Archive 27 empty databases

Archive empty databases to reduce workspace clutter: Fireflies Meeting Transcripts, db.Client_NS Hub_Files, Status Updates, db.Client_NS Hub_ChangeLog, db.Client_NS Hub_Q&A and 22 more.

Reduces noise in workspace navigation and improves search relevance.

Pillar: content_healthAffects: peripheral systems
low+15 pts

Establish regular workspace health review cadence

Run Workspace Pulse monthly to track maturity score trends, identify new risks early, and celebrate improvements. Share results with team leadership.

Creates accountability for workspace health and ensures continuous improvement rather than periodic cleanups.

Pillar: generalAffects: core systems
low+8 pts

Build automation to reduce manual burden on power users

Identify repetitive manual work in core systems and implement Notion automations, API integrations, or template systems to reduce effort.

Reduces burnout risk for key contributors and makes processes more sustainable.

Pillar: maturityAffects: core systems
low+2 pts

Review 25 stale reference databases

These reference databases are connected to active systems but haven't been updated in 60+ days: db.client_ResponsibilityMatrix, Database Glossary, Proof of Concept Files. Review for accuracy.

Prevents outdated reference data from being used in active workflows.

Pillar: content_healthAffects: supporting systems