← Cycles
design · c12archivedstarted Mar 10Auto draft — not yet reviewed

Projects as Modular Units

Why we did this

Qpoint had eight or more projects, each expert in something, but none knew what the others offered. Using two together meant knowing where everything lived.

What happened

Each of the four main projects now lists its neighbors: what each is for, when to use it, and where its data lives. AI sessions can now borrow across projects unaided.

In wordsDesign, market research, wireframing and the shared kit each say which neighbors they use and how.

Start here

At a glance
3
changes
0
conversations
3
decisions
0
outside helpers

What changed

The two changes that matter most, in plain words. Open any one to see it.

  1. 1

    Design, market research, wireframing and the shared kit each say which neighbors they use and how.

    Every core project lists its neighbors · came from Mark Parson

  2. 2

    Asked for a wireframe with real customer quotes, the wireframing project found the quotes on its own.

    The test case works · came from Mark Parson

Also in this cycle
  • The neighbor sections written here are still in use, and have grown. In words

How we got here

Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.

Someone said

From the record: no recorded conversation behind this one.

We decided

c12-D1 Documentation as the interface between projects, not a new server: plain file reads are enough for internal work. — Mark Parson

c12-D2 Peer to peer: no parent file and no central hub; each project lists only the neighbors it actually uses. — Mark Parson

So now

Design, market research, wireframing and the shared kit each say which neighbors they use and how.

Someone said

From the record: no recorded conversation behind this one.

We decided

No ruling needed: the work itself is the change.

So now

Asked for a wireframe with real customer quotes, the wireframing project found the quotes on its own.

Thanks to

People outside Qpoint first. Every thank-you points at something they said or made.

MP
Mark Parson
Qpoint team

Framed projects as specialists with clean interfaces

His prompt described each project as a specialist one project can call on from another, gave the wireframe-with-customer-quotes example, and asked how to make that crosstalk normal.

All images

Every picture from this cycle. Click any one to step through them all.

The pairs

Everything captured · 0

The full record 3 decisions · 4 key-change entries · 317 words · 0 captures

The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.

Open the record for c12 →

Qpoint Brand Style Guide