--- url: https://docs.lodestone.pm/00-introduction-to-lodestone.md --- # Introduction to Lodestone *What it is, how it thinks, and how the pieces fit together* *** ## What Is Lodestone? Lodestone is a product management platform designed to help product managers turn messy, fragmented feedback into clear, coherent plans — and share those plans through strong narratives and presentations. At its core, Lodestone helps PMs: * Capture product ideas from real conversations * Shape those ideas into structured plans * Communicate WHAT is being built, WHY it matters, and WHEN it is coming * Achieve organizational alignment through storytelling Lodestone is built first and foremost for the **individual Product Manager**, while steadily evolving to support **Product Leaders managing teams of PMs**. *** ## What Lodestone Is Not Lodestone is intentionally focused. It is not: * **A developer ticketing system** — it doesn't replace JIRA, Asana, or Azure DevOps * **A project management system** — it doesn't replace MS Project, Monday.com, or task-based execution tools * **A workflow enforcer** — it doesn't mandate rigid processes or linear paths Lodestone sits between customer reality and delivery execution. It focuses exclusively on the product management layer — capturing intent, building plans, and communicating them clearly. *** ## The Core Belief Lodestone is built on a simple but strong belief: > Product managers do their best work when they spend more time sharing and refining plans with stakeholders, not assembling artifacts. A user knows Lodestone is working for them when: * They are creating and sharing plans more frequently * They are presenting roadmaps and strategies more often * They are spending less time formatting and more time aligning people *** ## The Planning Stack Lodestone is organized around core objects that reflect how product work actually unfolds in the real world: | Object | What it does | |---|---| | **Discovery** | Combines customer, usage, and competitive evidence into backlog opportunities | | **Extracts** | Raw ideas surfaced from meeting transcripts and competitive reports using AI | | **Backlog** | Concrete initiatives a product team may pursue, organized by type (Features, Epics, Bugs, etc.) | | **Documents** | Written artifacts that explain and justify Features | | **Roadmaps** | Narrative plans that explain WHAT is being built and WHY | | **Releases** | Progress views that communicate WHEN things are happening | | **Strategy** | Long-term investment decisions that force tradeoffs over time | | **Competitive Intelligence** | AI-generated competitor tracking and market analysis | | **Financial Forecast** | Financial modeling (NPV, ROI, IRR) for individual Features | | **Bento Grids** | Visual release summaries designed for sharing with stakeholders and customer-facing teams | This stack is **not prescriptive**. Users may start at any point depending on their needs. A PM might begin by uploading a customer call transcript, or they might start by sketching out a roadmap. Lodestone accommodates both. *** ## WHAT, WHY, and WHEN One of Lodestone's most important mental models is the separation of planning concerns. Different modules answer different questions: * **Roadmaps** answer: WHAT are we building, and WHY does it matter? * **Releases** answer: WHEN is it happening, and how is progress tracking? * **Strategy** answers: Where are we intentionally investing over time, and what tradeoffs are we making? Keeping these questions separate prevents overloaded artifacts and keeps communication clear. A roadmap that tries to also track delivery status becomes harder to share. A release board that tries to explain strategic rationale becomes harder to read. *** ## Objects Over Workflows Lodestone is intentionally **object-centric**, not workflow-centric. Product teams don't follow linear paths. Planning is iterative. Different people enter the system at different stages. Rather than enforcing a single "right" flow, Lodestone lets: * Features exist independently of any roadmap or release * Objects relate to each other flexibly * Structure emerge through usage, not prescription This means you're never forced to complete one step before starting another. The platform adapts to how you actually work. *** ## AI as an Assistant, Not an Author AI is woven throughout Lodestone — in Extracts, Documents, Roadmaps, Strategy exports, and more. It exists to: * Eliminate blank-page work * Speed up iteration * Surface insights from raw data AI does **not** replace human judgment. All AI-generated content in Lodestone is editable, clearly marked, and designed as a starting point — not a finished product. You stay in control of everything the platform produces. *** ## Key Design Principles A few principles shape how Lodestone behaves across every module: **Guidance over enforcement** — Lodestone provides strong defaults and opinionated visualizations, but rarely forces a single way of doing things. You can adapt it to your context. **Narration over execution** — Execution lives in delivery tools. Lodestone exists to explain and align. Its outputs are presentations, exports, and shared artifacts — not tickets or task lists. **Scarcity as a forcing function** — Where Lodestone does enforce constraints (like exactly three Strategy dimensions), it does so intentionally. Constraints force meaningful choices. When everything is a priority, nothing is. *** ## The Dashboard When you log in to Lodestone, the Dashboard is the first thing you see. Called the **Command Deck**, it organizes recent workspace activity into five columns — Collecting Data, Processing Data, Making Plans, Aligning Plans, and Executing Plans — reflecting the full product lifecycle at a glance. New items (objects created or updated since your last visit) are highlighted automatically. The columns can be reordered by drag-and-drop to match your workflow. See the Dashboard module documentation for full details. *** ## Copilot Copilot is Lodestone's built-in AI assistant, accessible from the **Copilot** button in the left-hand navigation on every page. It answers questions about the platform and product management best practices, and can take actions in your workspace — creating features, building roadmaps, generating documents — when you ask it to. See the Copilot module documentation for full details. *** ## How the Module Docs Are Organized Each Lodestone module has four documentation pages: * **Overview & Concepts** — what the module is, why you'd use it, key terminology * **How-tos & Workflows** — step-by-step guides for the main user journeys * **Advanced Features & Customization** — deeper configuration, integrations, and power-user options * **Troubleshooting & FAQs** — common problems, edge cases, and answers to frequent questions If you're new to Lodestone, start with the Overview & Concepts page for whichever module you're working with. If you already know what you need to do, go straight to How-tos & Workflows. *** *This documentation covers the current Lodestone platform, updated to reflect all modules including Competitive Intelligence, Financial Forecast, Bento Grids, and the Lodestone API.*