Intake
Intake is where MikroLens collects product signals before they become owned work.
Use it for customer requests, support patterns, sales notes, internal asks, market observations, and product ideas. A signal is not a commitment. It is a piece of evidence the team may decide to act on later.
What Belongs in Intake
Section titled “What Belongs in Intake”Good intake records answer a few simple questions:
- Who is affected?
- Where did the signal come from?
- Why might it matter?
- What outcome would make this useful?
- Is there a timeline or urgency attached?
Keep the record short. Intake should make the signal visible without forcing premature planning.
Fields
Section titled “Fields”Each signal has:
- title;
- summary;
- source;
- urgency;
- expected timeline;
- status: Open or Pulled.
Use the summary for evidence, not a finished solution. The signal can be shaped later if it proves worth attention.
Pulling a Signal Into Work
Section titled “Pulling a Signal Into Work”When a signal is ready for a team to consider, pull it into a target Space. MikroLens creates an unplanned Idea in that Space’s Inbox and marks the original intake record as Pulled.
The new work item keeps the title and summary, so the original evidence travels with it.
From there, the team can:
- shape the idea in the Space;
- link a Strategy, Evolution, or Note document;
- move the work into Now, Next, or Later;
- assign owners and track blockers;
- archive the work if it no longer matters.
Good Practice
Section titled “Good Practice”Treat intake as a sensing layer. Keep it open enough to collect real signals, but do not let it become a second backlog.
Pull signals forward when they need ownership, strategy, or planning. Leave them in Intake when they are useful context but not yet product work.