Properties available for a Chunk depend on the Chunk type. For example, Tasks have Due Date and Progress, while Hypotheses won’t have those.
Note: Chunks are available starting from the PRO plan.
Read also: Chunks overview
Chunk types
By default, there are the following Chunk types:
Problem;
Idea;
Task;
Observation;
Hypothesis.
Plus, there are uncategorized type Chunks that are created when you copy or move documents containing Chunks from another Workspace. You can’t assign this type manually.
Tags
Assigning a tag to a Chunk makes this Chunk available on this tag page for everyone who has access to the tag.
When a Chunk is created inside a document, all documents’ tags are added to the Chunk automatically.
When a Chunk is created from a Tag page, it gets this tag assigned.
You can adjust tags manually inside the Chunk or from the Dashboard.
Owners
You can assign someone ownership to a Chunk from the list of your Workspace contributors and viewers. People you assign will receive an email notification.
How the score is calculated
All Chunk types except Observations and Hypotheses have the ‘Score’ section.
A score is calculated automatically and helps to prioritize efforts based on assumed business and customer values.
To calculate it, you’ll need to have Effort and at least a Business value or Customer value defined:
The formula is: Score = Value/Effort * 100%
The bigger the value, the bigger the score. The bigger the effort, the lower the score.
Related chunks
With related Chunks, you can:
Connect different chunks to one another logically (e.g., problems with a task or an observation with an idea)
Show dependencies between different tasks (e.g., indicate blockers)
To change the connection type, click on the dots on the right of the related Chunk:
Blocker and Waiting on are the opposites: if Chunk 1 is a blocker for Chunk 2, Chunk 2 will be automatically waiting on Chunk 1 to be completed.
Comments
Here, you can start threads and discuss anything related to the Chunk.
Occurrence
The occurrence table lists all documents that use this specific Chunk. This information can be helpful when:
You are considering Chunk’s priority. For example, if the problem reproduces across different journeys, it might be considered more important to be fixed.
You are doing a cleanup and checking if the Chunk is needed.