# Solutions for product managers

## Clear the customization backlog.

Your backlog is full of layout requests. “Can you add a column.” “Can we see this as a chart.” “Can you group by region.” These aren't features. They're view preferences. Let users handle them.

## Anchor Strategy **Product backlog**

| Item               | Priority | Status    | Team   | Sprint | Effort |
|--------------------|----------|-----------|--------|--------|--------|
| Dashboard filters   | High     | In sprint | Core   | S24    | 3 pts  |
| CSV export         | Medium   | Backlog   | Core   | —      | 2 pts  |
| Mobile nav         | High     | In sprint | Design | S24    | 5 pts  |
| Webhook support    | Low      | Backlog   | Infra  | —      | 8 pts  |
| Onboarding flow    | High     | Review    | Growth | S24    | 3 pts  |

### Backlog

**CSV export**  
CoreBacklog

**Webhook support**  
InfraBacklog

### In sprint

**Dashboard filters**  
CoreIn sprint

**Mobile nav**  
DesignIn sprint

### Review

**Onboarding flow**  
GrowthReview

One backlog. PMs and engineers each shape their view.

## The problem

Half your sprint planning is spent on UI customization. Not features. Not architecture. Layout variants.

Backlog full of “show this data differently” tickets.

Every user segment wants a different default view.

Sprint planning dominated by dashboard customization, not real features.

## How ShapeKit fits

**Ship the data layer.** Define your data model, business rules, and core views. Deploy without predicting every layout variant.

**Users shape what they see.** They describe the view they want. Columns rearranged, charts swapped, filters applied. No ticket filed. No sprint interrupted.

**Your backlog shrinks.** Customization requests drop. Your sprints focus on features that actually need engineering.

## What you get

### Backlog focused on real features

Layout requests disappear. Your team ships product, not variants.

### Usage data for roadmap decisions

See which views users create. Know what matters to them without guessing.

### Faster iteration cycles

Ship a base view. Users reshape it. You learn what works. Iterate on signal, not assumptions.

## Common questions

### Can I control what's shapeable?

Yes. You define constraints per skill. Lock down data integrity and business logic. Users only shape what you allow.

### What analytics do I get?

You see which views users create, which skills get reshaped most, and where users get stuck. Real product signal.

### Does it work with our existing app?

ShapeKit skills embed into your app. You don't rebuild. You add shapeable components alongside your existing UI.

### How do users actually reshape things?

They click the Shape button and describe what they want. AI generates the view within your constraints. No settings menus. No configuration panels.

## Get your backlog back. Ship features, not layouts.

Let users shape their own views. Your team focuses on what actually needs engineering.