Skip to content
CuikDocumentation

Why this approach?

Behind the product: the principles, references and choices behind project tracking in Cuik.

2 min readUpdated 25/09/2026
On this page
  1. Connect the work to an outcome
  2. Separate the goal from its measurement
  3. Keep approval with the work concerned
  4. Show details when they become useful

This page explains the design choices behind project tracking in Cuik. For actions in the interface, see the project management guide.

Connect the work to an outcome

A card describes what needs doing. A goal describes the intended change. We suggest connecting the two, with optional missions to group work that needs coordination.

This structure is a Cuik design choice, not a universal framework. The boundary between a mission and a card depends on the project: rewriting one page may fit in a card; updating twenty pages with several contributors may warrant a group.

Separate the goal from its measurement

Atlassian’s Goals, Signals, Measures framework distinguishes a goal, signs of change and the measures used to observe them.

For example: increasing qualified enquiries is the goal; more relevant visits are an intermediate signal; enquiries from organic traffic, qualified in the sales process over an agreed period, provide an outcome measure.

We use this framework to explain what to observe. It complements card organisation without requiring extra fields. These concepts currently live in project notes; indicators are not automatically linked to goals.

Keep approval with the work concerned

Asana distinguishes approval, requests for changes and rejection. We retain the principle of an explicit response, adapted to the simplicity of Cuik cards.

A question seeks information or a choice. An approval seeks agreement on something proposed or completed. Approval stays on the relevant card, with a next step: resume work or complete the card. This keeps the request, context and response together.

Show details when they become useful

Progressive disclosure, described by Nielsen Norman Group, keeps common functions accessible while revealing specialised options on demand.

In Cuik, start with a title. Descriptions, subtasks, dependencies and approval requests can then enrich the card. Optional functions live under Add.

These references inform our choices; they do not prove this organisation is superior for every SEO project. You can keep your own method, use cards alone or work only with analysis and reports. All features remain available.