Skip to main content
How to use Brand Visibility Execution

Execution sits on top of your Scorecard diagnostic. Use Command Hub to govern initiatives; use Performance Tracking to show how implemented work aligns with GEO movement over time.

1. Prerequisites and entry

  1. Confirm an active Core or Nexus subscription — Execution does not sell standalone.
  2. From the dashboard, open the roadmap or execution entry point on the brand insight you want to govern (the URL carries an `insight` id — keep it when you share links internally).
  3. Decide who owns the workspace: typically the CMO chief of staff or PMO lead keeps rows current while pillar VPs approve scope.

2. Command Hub — Strategic Project Workspace

  1. Use the GEO scoreboard strip to filter initiatives by primary dimension; highlight the row set you will discuss in the weekly marketing ops forum.
  2. Work the execution pillar chips (Authority & Trust, Narrative Precision, Ecosystem Presence) to sequence work the way the CMO office already thinks about horizons.
  3. For each initiative, keep title, owner, pillar, primary GEO dimension, status, and dates honest — this is the system of record for what shipped versus what is still open.
  4. Capture Impact to GEO Dimension on a scale of 10 so leadership can see which programs you believe move the needle hardest.
  5. Use Details to read the full row in one place; use Add project when a new initiative is funded and should appear in the same governance set.
  6. Sync when prompted so portfolio state persists to the saved diagnostic — treat a successful sync the same way you treat a closed Jira epic.

3. Performance Tracking — trends and attribution view

  1. Stay on the same `insight` as Command Hub so charts and initiative tables reference one brand diagnostic.
  2. Pick the time lens that matches your meeting (rolling 30 / 60 / 90 days or calendar MoM, QoQ, YoY) before you present so the axis does not shift mid-review.
  3. Read the GEO trend chart as your score movement spine; narrate inflection points with the same dates you used in Command Hub status updates.
  4. When strategic projects exist, review the implementation table and attributed column as an illustrative split — use it to steer conversation, not as a substitute for finance sign-off.
  5. Reconcile reruns with leadership: if diagnostics refresh after a major milestone, capture what changed in the storyline you take to the board.

4. Leadership operating rhythm

  1. Monthly: pillar VPs confirm open versus implemented rows and pick the next three bets tied to weakest dimensions.
  2. Quarterly: CMO reviews Command Hub plus Performance Tracking on one canvas — decide continue, pivot, or stop based on score and delivery truth.
  3. Board prep: export Scorecard artifacts from the diagnostic layer; cite Execution tables only when you want to show governance between reruns.

Loading…