Connecting Strategy to Execution

Most engineering organizations run two disconnected systems. Strategy lives in slide decks, spreadsheets, or an OKR tool. Execution lives in the project management board.

The link between them, which work is actually serving which objective, exists only in people's heads.

So when a leader asks "which goal is this epic delivering?" or "what are we investing against this objective?", the honest answer is usually a manual reconstruction.

Kindor's new Portfolio section closes that gap. It's a strategy-first surface where you define what the organization is working toward and connect it directly to the engineering work underneath. It introduces two capabilities that work together: Custom Fields and Goals.

Custom Fields: Enrich your work where it matters

Custom Fields let you attach your own metadata to projects and epics directly inside Kindor and then put it to work.

• Enrich your data. Add fields like business line, risk tier, capitalizable, or compliance scope on top of the data Kindor already syncs from your tools. You're layering your organization's vocabulary over real, live work, not maintaining a separate spreadsheet.

• Apply it fast, across many items. Fields are edited inline in a portfolio table view, so you can label dozens of epics or projects in seconds instead of opening each item and clicking through a properties panel.

• It powers Kindor's analytics. Fields like "Capitalizable" plug straight into downstream views such as the Financial Analysis module. Now you can specify whether to consider all work under a project or epic as capitalizable.

Goals: A configurable Strategic Layer

Goals introduces a first-class strategic entity that you create, manage, and name in your own language.

Some teams run OKRs. Others use Rocks, Milestones, or Strategic Themes. Rather than force one framework, Kindor lets you rename the entity to match how your organization already thinks. Whatever you call it, the capability is the same.

Once your goals exist, you connect them to the work meant to deliver them:

• Map epics to goals inline, directly from the Epics table.

• Map whole projects to goals for teams that treat projects as scoped, time-boxed deliverables.

• Track lifecycle as goals move through Active, On hold, Completed, and Archived.

Portfolio is intentionally the strategy-first surface, the place to express intent and structure. The day-to-day execution view, where goal coverage, cost, and effort get rolled up across all the mapped work, lives in Kindor's execution dashboards, which are built for exactly that kind of live analysis.

Custom Fields and Goals are the foundation of a larger idea we call Strategy-to-execution visibility: a clean line of sight from a high-level objective all the way down to the epics, projects, cost, and effort flowing into it.