INA Scope (INA Granularity)
Product term: Scope
Category: concept
Definition
The size and complexity boundary of a single INA. Too small: management overhead. Too large: unclear ownership. Typically, an INA takes 1 day to 2 weeks of work. Includes all sub-tasks, decisions, and dependencies bundled together.
Key Points
- •Optimal INA size boundary
- •Typically 1 day to 2 weeks work
- •Larger: unclear ownership
- •Smaller: too much overhead
- •Includes dependencies and decisions
- •Impacts routing and accountability
Frequently Asked Questions
How do I know if an INA is the right size?
One person should be able to fully own it. Can you explain it in 2 minutes? Good size. Need a presentation? Too big.
What if the work is only 2 hours?
Bundle it with related work into a full day. Or use sub-tasks within a larger INA.
Can an INA span multiple people?
Yes, if it's coordinated work. But one person should own it end-to-end.
What if the work is 3 months?
Break it into smaller INAs. Can be chained (INA A → INA B → INA C) or parallelized.
Related Terms
INA — Intelligence-Native Artifact
The atomic unit of work in an INO. A smart, self-routing digital object with fou...
Routing Rules Engine
The intelligent system that directs INAs, messages, and decisions to the right p...
Impact Ledger & Bounty Protocol
A transparent, immutable record of who contributed to what work and what value w...
Payload
The actual deliverable or work product within an INA. The "thing" being created:...
Learn more about Intelligence-Native Organizations