Use casesProject management

Turn a complex launch into a living project Map.

Project management is not only tasks and deadlines. Real projects depend on decisions, risks, evidence, meeting updates, and context that needs to survive across weeks. BaseHalf gives those pieces a visible surface.

PromptCreates 3 Points

Turn this project into a Map with charter, workstreams, decisions, risks, meeting notes, open questions, and weekly review Points.

  • Charter
  • Workstreams
  • Decision log
Workflow

From one request to reusable context

01

Create the charter

Start with the goal, deadline, non-goals, owners, and constraints so every later Point has an anchor.

02

Split workstreams

Separate product, design, engineering, data, support, docs, and launch communication into Points with their own context.

03

Promote decisions

Turn important choices into Decision Points with alternatives, reasoning, evidence, and revisit conditions.

04

Keep risks active

Write risks with triggers, owners, mitigations, and fallback paths instead of vague warnings.

05

Review weekly

Use a Weekly review Point to summarize what changed, what is blocked, and what context should guide the next move.

Complex scenario

Example: onboarding launch across six workstreams

A team is shipping a new onboarding flow while changing plan selection, analytics, help docs, support macros, and launch messaging. The task list is clean; the context is not.

01

Map the launch

Create a charter Point and workstream Points for product flow, engineering, data, support, docs, and go-to-market.

02

Capture the critical decision

Create a Decision Point for whether plan selection stays inside onboarding or moves to billing settings.

03

Connect the risk

Reference the billing integration risk to the decision, API contract notes, engineering plan, and launch milestone.

04

Feed the weekly update

Draft the stakeholder update from connected decisions, risks, meeting notes, and workstream Points.

Map structure

What the workspace should contain

Charter

Goal, scope, non-goals, deadline, owners, and constraints.

Workstreams

Product, design, engineering, data, support, docs, and launch communication.

Decision log

Stable choices, alternatives, evidence, and conditions that would reopen a decision.

Risk register

Active risks with triggers, mitigations, owners, and review dates.

Outcomes

What should exist after the work

  • A project Map that explains why the work is moving, not only what is assigned.
  • Decision and risk memory that survives meetings and team handoffs.
  • Weekly reviews that can be drafted from connected context instead of recollection.