DOCSEARCHbyAlgolia
Submit Docs

Core & Explore Methodology

website·Indexed 31 days ago

https://coreexplore.net/docs/getting-started/core-explore-in-5-minutes

A system for running startups and organizations designed to bridge the gap between working hard and making progress. The methodology utilizes two tracks—Core and Explore—incorporating specific roles (Explore Lead, Explorer), a Kanban-based Explore Board, and a weekly cadence of Meta and Explore meetings to manage learning and execution.

Tokens
57K
Snippets
53
Records
381
Agent score
50%

What's inside Core & Explore

  1. Overview of the Core & Explore framework

    Core & Explore is an operating system for startups designed to separate known execution (Core) from unknown discovery (Explore). It focuses on increasing the cadence of learning cycles to find product-market fit faster, scale revenue, and manage growth without breaking existing validated models. The framework is built on two first principles: that startups are searching for a business model rather than executing one, and that business outcomes are more important than shipping outputs.

  2. Overview of the Core & Explore methodology

    Core & Explore is a scientific, systematized methodology created in 2014 to bridge the gap between traditional business execution and the reality of startups. While traditional systems measure execution (assuming the path is known), Core & Explore focuses on 'figuring things out' through a systematic, experimental approach to unknowns. It is designed to help startups navigate resource constraints and prioritization challenges across three primary phases: finding product-market fit, transitioning to growth, and scaling that growth.

  3. Overview of the Core & Explore Notion template

    The Core & Explore Notion template provides a single workspace to manage the end-to-end process of Core & Explore. It integrates goals, projects, and tasks to maintain visibility across the organization. The template includes the following components:

    • OKRs: Tracking for Core and Explore OKRs at quarterly, monthly, and weekly levels, linking objectives and key results to specific projects.
    • The Explore Board: A six-column lifecycle tracker for Explore Projects consisting of: Up for Debate, Next Up, Actioning, Measuring, Done, and Conclusions Discussed.
    • Meetings: Dedicated sections for agendas and notes for Meta Meetings and Explore Meetings.
    • Projects: Project pages that link each initiative to its Project Intent, Success Measure, and Learnings.

  5. Overview of the Core & Explore meeting framework

    The Core & Explore system is driven by two essential meetings: the Meta Meeting and the Explore Meeting. All other meetings (such as prep meetings, ideation sessions, and standups) are optional and exist only to support these two primary drivers. These meetings typically follow a weekly cadence to maintain momentum and ensure a consistent rhythm of learning, adjusting, and acting.

  6. Understand the Go-To-Market (GTM) phase in Core & Explore

    Go-to-market is a phase (not a funding stage) focused on moving from 'knowing who buys and why' to 'selling predictably.' The goal is to transition a process from 'working once' to 'working repeatedly.' In this phase, the Core & Explore framework is used to maintain discovery (Explore) while codifying the repeatable parts of the sales motion (Core).

  7. Use an Ideation Session to rapidly populate the Explore Board

    An ideation session is a focused, ad-hoc meeting designed to generate a high volume of Explore project ideas and perform an initial prioritization pass. It is distinct from the regular Explore Meeting and is used specifically when the team needs fresh ideas faster than the weekly cadence can provide, such as when facing a new objective or a thin project pipeline.

  8. Define success using the Meta Milestone

    In the Core & Explore framework, the ultimate measure of success is achieving the objectives defined in the Meta Milestone. The Meta Milestone serves as the 'north star' and is a lagging indicator, meaning its achievement is only confirmed at the end of a period. All other metrics within the framework are considered leading indicators used to track progress toward this goal.

  9. Implement the Core & Explore dual-track system

    The Core & Explore system separates work into two parallel tracks based on whether the path to success is known or unknown. Both tracks must align with a single 'Meta Milestone'—the most important outcome for the current strategic period.

    • Core Track: Focuses on scaling and execution of validated work. Success is defined by delivering committed outcomes using specific OKRs and defined initiatives.
    • Explore Track: Focuses on search and discovery. Success is defined by gaining validated insights (confirming or invalidating hypotheses) through Explore projects, regardless of whether the project 'ships' a feature.

  10. Manage the Explore board backlog

    The Explore board backlog serves as a holding area for projects that have merit but are not currently prioritized due to capacity, shifting Explore OKRs, or lack of immediate relevance. To prevent the backlog from becoming a 'dumping ground' that creates signal degradation and false optionality, it must be regularly maintained.

  11. Understand Core Projects in Core & Explore

    A Core Project is defined as planned work where the outcome is known and the path to achievement is clear. Unlike Explore Projects, which are experimental, Core Projects focus on execution. They are the initiatives that drive Core OKRs and are managed within an organization's existing project management system rather than on the Explore Board.

  12. Understand the Core Team role and responsibilities

    The Core Team is responsible for executing planned, predictable work with high confidence that activities will produce expected outcomes. This includes day-to-day operations, planned features, and repeatable business processes. In the Core & Explore framework, the Core Team specifically executes on Core OKRs.

    Examples of Core work include:

    • Engineering teams shipping planned roadmap features.
    • Sales teams executing a known playbook.
    • Support teams handling customer requests.