Management View — Jyri Petronen
Everything happening in the company, in one view.
Week of June 16, 2026
The Atelier³
The Atelier³
Needs Your Decision
3
items waiting for Jyri
Blocked Items
2
team is stuck
Overdue Tasks
1
past deadline
Completed Today
5
tasks delivered
🔴 Needs Your Decision
Critical
Approve proposal for Client X — deadline today
Flagged by Diana Akami
High
Confirm budget for LinkedIn paid campaign
Flagged by Ivan Medvedev
High
Approve new outreach messaging for Q3
Flagged by Houssem El Behi
🚧 Blocked Items
High
Market research — Finland SaaS segment
Ivan — waiting for access to analytics tool
Medium
Outreach sequence — DACH region
Houssem — needs approved offer document
⚠️ Overdue
Overdue
Weekly growth report — Week 23
Ivan Medvedev — was due Friday
👀 Waiting for Your Review
Review
Competitor analysis — 5 key players
Submitted by Diana Akami
Review
Asana operational system setup — complete
Submitted by Kourosh Khajeh
👥 Team Pulse
Kourosh
Co-Founder & CTO
Tara
Assistant Manager
Diana
Business Development
Houssem
Business Development
Ivan
Head of Growth
📈 Sales This Week
Prospects contacted24
Meetings booked3
Proposals sent1
Pipeline items active8
🎯 This Week's Goal
Complete Asana setup, run first live week of the operational system, and book 3+ discovery calls.
Progress60%
✅ Completed Today
| Task | Owner | Deliverable | Status |
|---|---|---|---|
| Operational system document — V1.0 | Kourosh | PDF + HTML delivered | Completed |
| Prospect list — Nordic B2B SaaS (30 companies) | Diana | Google Sheet linked | Completed |
| LinkedIn outreach — 12 contacts | Houssem | CRM updated | Completed |
| Asana project setup — Team Operations | Tara | Asana section live | Completed |
| Growth channel audit — Q2 | Ivan | Report in Drive | Completed |
Team Roles & Responsibilities
Everyone's role, daily tasks, authority, and expected output.
Jyri Petronen
Founder & CEO
Reports to: Board / Himself | Team reports to: Everyone
Main Responsibilities
- Company direction & strategy
- Final client approvals
- Team performance
- Budget & hiring decisions
Daily
- Review management view
- Clear review queue
- Decide on escalations
Can Decide Independently
- Everything
Weekly Output
- Week priorities set Monday
- All reviews cleared
- Pipeline reviewed
Kourosh Khajeh
Co-Founder & CTO
Reports to: Jyri
Main Responsibilities
- Technology strategy
- Operational systems
- Asana / task management
- Execution quality
Daily
- Review all task statuses
- Ensure tasks are structured
- Escalate blockers to Jyri
Can Decide Independently
- Tech choices
- Process design
- Tool config
Weekly Output
- System running & updated
- Weekly plan shared
- Blockers resolved
Tara Ghanizadeh
Assistant Manager
Reports to: Jyri & Kourosh
Main Responsibilities
- Day-to-day coordination
- Scheduling & admin
- Task tracking & follow-up
- Document management
Daily
- Check task statuses
- Flag overdue items
- Coordinate meetings
Can Decide Independently
- Scheduling
- Internal comms
- Admin decisions
Weekly Output
- Nothing missed
- Team coordinated
- Jyri's time protected
Diana Akami
Business Development Manager
Reports to: Jyri
Main Responsibilities
- Prospecting & lead gen
- Outreach execution
- Pipeline & CRM management
- Meeting booking
Daily
- Execute outreach tasks
- Update CRM after every contact
- Follow up open leads
Can Decide Independently
- Copy adjustments
- Lead prioritisation
Needs Approval For
- New market direction
- Pricing / offer changes
- Formal proposals
Houssem El Behi
Business Development Manager
Reports to: Jyri
Main Responsibilities
- Prospecting & lead gen
- Outreach execution
- Pipeline & CRM management
- Meeting booking
Daily
- Execute outreach tasks
- Update CRM every contact
- No duplicate with Diana
Can Decide Independently
- Copy adjustments
- Lead prioritisation
Needs Approval For
- New market direction
- Pricing / offer changes
- Formal proposals
Ivan Medvedev
Head of Growth
Reports to: Jyri
Main Responsibilities
- Growth strategy
- Marketing & brand visibility
- Inbound lead generation
- Analytics & reporting
Daily
- Monitor campaigns
- Track key metrics
- Flag underperformance early
Can Decide Independently
- Channel tactics
- Content direction
- Experiment design
Needs Approval For
- Paid campaign budget
- Major brand changes
- External partnerships
Task Rules
How tasks are created, delivered, and reviewed at The Atelier³.
Creation
Delivery
Review
A task is not ready to assign until the person can start working without asking more than one clarifying question. If the task is unclear — rewrite it before assigning.
Checklist Before Assigning
- Clear, specific task title
- One owner — not two
- Priority level assigned
- Deadline is a date — not "ASAP"
- Context explains why this task exists
- Objective is clear and measurable
- Instructions specific enough to act on
- Expected deliverable defined
- Success criteria written
- Relevant files or links attached
- Reviewer named
Priority Levels
| Priority | Meaning | Response |
|---|---|---|
| Critical | Blocking clients, revenue, or team | Same day |
| High | Important and time-sensitive | Within 24 hours |
| Medium | Important but not urgent | Within 48 hours |
| Low | Nice to have. No hard deadline. | When possible |
Task Creation Template
Template
TASK NAME:
[Short, action-oriented title]
OWNER: [One person only]
PRIORITY: [ ] Critical [ ] High [ ] Medium [ ] Low
DEADLINE: [Date — not "ASAP"]
──────────────────────────────
CONTEXT
Why this task is needed. What happens if not done.
──────────────────────────────
OBJECTIVE
What we want to achieve. What success looks like.
──────────────────────────────
INSTRUCTIONS
1.
2.
3.
──────────────────────────────
EXPECTED DELIVERABLE
Exactly what should exist when done.
──────────────────────────────
SUCCESS CRITERIA
- [ ]
- [ ]
──────────────────────────────
REVIEWER: [Name]
LINKS / FILES: [Attach materials]A task is not completed by saying "done." It is completed when the result is visible, linked, and confirmed against the original deliverable.
Checklist Before Marking Complete
- Result exists and is accessible via link
- Deliverable matches what was requested
- Short summary of what was done is written
- Reviewer is notified
- Missing items flagged honestly
- Next step suggested if applicable
Never acceptable as a delivery:
Writing "done" with no link, no summary, and no context. This is not a delivery — it is a notification that something may or may not have happened.
Writing "done" with no link, no summary, and no context. This is not a delivery — it is a notification that something may or may not have happened.
Task Delivery Template
Template
TASK: [Task name]
OWNER: [Your name]
STATUS: [ ] Completed [ ] Partially [ ] Blocked
──────────────────────────────
WHAT WAS DONE
Short summary of work completed.
──────────────────────────────
DELIVERABLE LINK
[Link — or explain exactly where result is]
──────────────────────────────
KEY RESULT
Main outcome in 1–2 sentences.
──────────────────────────────
WHAT IS MISSING
Be honest. Say clearly if anything is absent.
──────────────────────────────
NEXT STEP
What should happen next. Who acts.
──────────────────────────────
NEEDS REVIEW FROM: [Name]Every task in "Waiting for Review" must be reviewed within 24 hours. Give clear, specific feedback — not just "needs work."
Review Statuses
| Status | Meaning |
|---|---|
| Approved | Complete. Result accepted. |
| Needs Edits | Good direction — specific changes required. |
| Missing Info | Key output absent. More work needed. |
| Wrong Direction | Does not match objective. Restart. |
| Reopened | Previously approved — rework needed. |
| Completed | Final. Fully done. No further action. |
What the Reviewer Checks
- Was the task completed per the instructions?
- Is the deliverable visible and accessible?
- Does quality meet the standard?
- Is anything missing or incorrect?
- Does the result solve the original objective?
Review Feedback Template
Template
TASK: [Task name]
REVIEWER: [Your name]
STATUS:
[ ] Approved
[ ] Needs Edits
[ ] Missing Information
[ ] Wrong Direction
[ ] Reopened
[ ] Completed
──────────────────────────────
WHAT IS WRONG OR MISSING
Specific explanation — not "needs to be better."
Write exactly what is wrong or absent.
──────────────────────────────
WHAT NEEDS TO CHANGE
1.
2.
3.
──────────────────────────────
DEADLINE FOR REVISION: [Date]
REVIEWER: [Name]All Templates
Copy and use these in Asana, Notion, Slack, or any tool your team uses.
Daily Report
Daily
DAILY REPORT — [Name] — [Date]
1. COMPLETED TODAY
Task name — Link to result
Task name — Link to result
2. IN PROGRESS
Task — status — expected completion
3. BLOCKED
Task — what / why — what I need
4. NEED FROM JYRI / TEAM
Decision needed:
Information needed:
Help needed:
5. TOMORROW'S PLAN
1.
2.
3.Weekly Report
Weekly
WEEKLY REPORT — [Name] — Week of [Date]
WEEKLY GOAL:
[What was the goal you were given?]
COMPLETED:
Task — Link to result
NOT COMPLETED:
Task — Reason — Current status
WHY NOT COMPLETED:
Honest explanation.
MAIN RESULTS:
2–3 sentences on what mattered.
BLOCKERS:
What slowed you down.
NEXT WEEK PRIORITIES:
1.
2.
3.Blocker Report
Blocker
BLOCKER — [Name] — [Date]
TASK: [Task name]
WHAT IS BLOCKED:
WHY IT IS BLOCKED:
WHAT I ALREADY TRIED:
WHAT I NEED:
WHO CAN UNBLOCK IT:
URGENCY:
[ ] Low [ ] Medium [ ] High [ ] Critical
RISK IF NOT SOLVED:
What happens to the task / client / company.Weekly Planning
Plan
WEEKLY PLAN — Week of [Date]
COMPANY GOAL THIS WEEK:
[One sentence — what does success look like?]
KEY PRIORITIES:
Client: Sales: Growth: Ops:
──── Per Person ────────────────
Kourosh — Goals / Deliverables / Deadline
Tara — Goals / Deliverables / Deadline
Diana — Goals / Deliverables / Deadline
Houssem — Goals / Deliverables / Deadline
Ivan — Goals / Deliverables / Deadline
────────────────────────────────
NEEDS JYRI'S DECISION:
1.
2.Daily Work Process
How every working day is structured at The Atelier³.
Daily Rhythm
Start of Day
Open Asana. Check assigned tasks. Confirm today's priorities. Note anything urgent.
Morning
Work on highest-priority tasks first. No context switching before the first task is done.
Midday
Update task statuses. Flag any blockers immediately — do not wait until end of day.
Afternoon
Continue task work. Deliver completed items. Notify reviewers.
End of Day
Send daily report. Update all statuses. Prepare tomorrow's plan before closing.
Rules
- Daily report is non-negotiable — sent every working day
- Statuses updated in real time — not at end of day
- Blockers reported same day — not tomorrow
- Deliverables linked when marking complete
- No task marked "done" without a visible result
- Unclear tasks flagged to Kourosh before starting
Daily Report Template
Daily
DAILY REPORT — [Name] — [Date]
1. COMPLETED TODAY
Task — Link
Task — Link
2. IN PROGRESS
Task — status — expected completion
3. BLOCKED
Task — what / why — what I need
4. NEED FROM JYRI / TEAM
Decision / Info / Help needed:
5. TOMORROW'S PLAN
1. 2. 3.Weekly Work Process
The weekly operating rhythm for the whole team.
Weekly Calendar
Monday
Weekly kickoff. Jyri sets company goal. Kourosh shares weekly plan per person. Priorities confirmed.
Tuesday – Thursday
Execution. Daily reports. Blocker escalation. Status updates in real time. Deliveries to reviewer.
Friday
Weekly reports submitted. Kourosh reviews system. Jyri reviews management view. Next week planned.
This Week's Plan — Example
Week of June 16 | Goal: Complete Asana setup and run first live week of operational system
Kourosh Khajeh
Co-Founder & CTO
Complete Asana projects & custom fields
Create Jyri's management view
Run team walkthrough — June 17
Tara Ghanizadeh
Assistant Manager
Move all active tasks into Asana
Set up meeting schedule for the week
Send daily reports every day
Diana Akami
Business Development
Contact 15+ new prospects
Book 2 discovery calls
CRM fully updated by Friday
Houssem El Behi
Business Development
Contact 15+ new prospects (separate from Diana)
Book 1+ discovery call
Resolve DACH outreach blocker
Ivan Medvedev
Head of Growth
Submit overdue Week 23 growth report
Launch one growth experiment
Resolve analytics tool access blocker
Blocker Process
How blockers are reported, escalated, and resolved.
The Rule: If you are blocked — report it the same day. Do not wait silently. Do not disappear. Do not work around the problem without telling anyone. A blocker reported late is a problem that grew unnecessarily.
Blocker Escalation Path
1 — Identify
You realise you cannot proceed. Try at least one thing to solve it yourself first.
2 — Report Same Day
File a blocker report in Asana. Set task status to "Blocked." Tag who can unblock it.
3 — Kourosh Reviews
Kourosh sees it in the daily check. If he can unblock it — he does. If it needs Jyri — it goes to the Jyri Review Queue.
4 — Jyri Decides
Jyri sees the blocker in his management view. He resolves it or delegates the resolution.
5 — Unblocked
Status updated. Owner continues. Resolution noted in the task.
Blocker Report Template
Blocker
BLOCKER — [Name] — [Date]
TASK: [Task name]
WHAT IS BLOCKED:
Exactly what cannot proceed.
WHY IT IS BLOCKED:
Missing info / waiting for someone /
tool issue / unclear instructions.
WHAT I ALREADY TRIED:
Be specific. Don't report before trying.
WHAT I NEED:
A decision / a file / clarification.
WHO CAN UNBLOCK IT: [Name]
URGENCY:
[ ] Low [ ] Medium [ ] High [ ] Critical
RISK IF NOT SOLVED:
What happens to the task / client / company.Urgency Guide
| Level | Meaning |
|---|---|
| Low | Can wait a few days |
| Medium | Needs resolution this week |
| High | Blocking progress today |
| Critical | Blocking client or revenue |
Task Status System
Every task uses the same statuses. No custom terms. No confusion.
Status Flow
Not Started
→
In Progress
→
Waiting for Review
→
Approved
→
Completed
In Progress
→
Blocked
→
(unblocked)
→
In Progress
Waiting for Review
→
Needs Edits
→
In Progress
Status Definitions
| Status | Meaning | Who Sets It | Required |
|---|---|---|---|
| Not Started | Assigned but not yet begun | Task owner | Owner, deadline |
| In Progress | Actively being worked on | Task owner | Owner, deadline |
| Waiting for Review | Done — awaiting reviewer | Task owner | Deliverable link + reviewer named |
| Needs Edits | Reviewer requested changes | Reviewer | Specific feedback + revision deadline |
| Blocked | Cannot proceed | Task owner | Blocker report filed same day |
| Completed | Reviewed, approved, done | Reviewer | Deliverable link visible |
| Cancelled | No longer needed | Jyri or Kourosh | Reason must be noted |
Non-Negotiable Rules
Every task must have
- A status — updated in real time
- One owner — not a group
- A deadline — a date, not "soon"
- A deliverable link when completed
Never acceptable
- Starting a task you don't understand
- Marking complete with no link
- Reporting a blocker at end of day
- Cancelling without a reason
Execution Quality Rules
What "good work" means at The Atelier³.
Good work IS
- Delivered on time
- Linked to a visible, accessible result
- Easy for anyone to check without asking questions
- Specific — not vague
- Solving the original objective
- Structured and clear
A task is NOT complete if
- There is no link or visible result
- The person only wrote "done"
- Output does not match what was requested
- Important information is missing
- Nobody can review it without more questions
- It does not solve the original objective
Quality Standard by Work Type
| Work Type | Minimum Acceptable Output |
|---|---|
| Research task | Structured document or spreadsheet with sources and findings |
| Outreach task | CRM updated + log of who was contacted and result |
| Client delivery | File sent + confirmation of receipt from client |
| Internal process | Document written + shared in correct folder |
| Growth / marketing | Report with metrics + recommendation based on data |
| System setup | Working system + brief on how to use it |
| Analysis | Written findings + recommendation + supporting data |
Asana Setup Brief
Exactly what needs to be built. Hand this to whoever is setting up Asana.
Projects & Sections
1. Team Operations
2. Sales / Business Development
3. Growth & Marketing (Ivan)
4. Current Clients (one per client)
5. Internal Systems (Kourosh)
6. Jyri Review Queue ⭐
Custom Fields (Add to All Projects)
| Field | Type | Options |
|---|---|---|
| Owner | Person | Jyri, Kourosh, Tara, Diana, Houssem, Ivan |
| Priority | Dropdown | Critical / High / Medium / Low |
| Status | Dropdown | Not Started / In Progress / Waiting for Review / Needs Edits / Blocked / Completed / Cancelled |
| Deadline | Date | Date picker |
| Deliverable Link | URL | Link field |
| Reviewer | Person | All team members |
| Blocker Note | Text | Required when Status = Blocked |
Delegation Plan
| Task | Owner | Deadline |
|---|---|---|
| Create all Asana projects and sections | Kourosh | June 14 |
| Add custom fields to all projects | Kourosh | June 14 |
| Add all 6 team members and set permissions | Kourosh | June 15 |
| Build task templates | Kourosh | June 15 |
| Create Jyri's management view | Kourosh | June 16 |
| Move all active tasks into Asana | Tara (supported by Kourosh) | June 16 |
| Team walkthrough — 30 minutes | Kourosh | June 17 |
| First full week live | All team | June 17–19 |
| First review and adjustments | Kourosh + Jyri | June 20 |
Launch Checklist
First version — test this week. June 14 to 19.
By June 14
- Share this system with all 6 team members
- Create all Asana projects and sections
- Add custom fields to all projects
By June 15
- Add all team members to Asana with permissions
- Build task templates in Asana
- Write and share first weekly plan (Week of June 16)
By June 16
- Create Jyri's management view
- Tara moves all active tasks into Asana
- Every team member has at least one task assigned
By June 17 — Go Live
- 30-minute team walkthrough
- Every team member sends first daily report
- First blockers go through system — not chat
June 17–19 — First Live Week
- Daily reports sent every day by everyone
- All task statuses updated in real time
- Deliverables linked when tasks completed
- Jyri uses management view daily
June 20 — First Review
- Did everyone send daily reports every day?
- Are all tasks in Asana with proper statuses?
- Did Jyri open the management view and understand what was happening?
- Were blockers reported through the system — not chat?
- Did everyone submit their weekly report on Friday?
The Five Rules of The Atelier³
1. Every task has one owner, one deadline, and one status. No exceptions.
2. A task is not complete until the result is linked and visible. "Done" is not a deliverable.
3. Blockers are reported the same day they appear. Not tomorrow. Not in chat.
4. Unclear tasks are rewritten before work starts. Never start a task you do not understand.
5. Daily reports are non-negotiable. They are how the team stays aligned without constant meetings.
1. Every task has one owner, one deadline, and one status. No exceptions.
2. A task is not complete until the result is linked and visible. "Done" is not a deliverable.
3. Blockers are reported the same day they appear. Not tomorrow. Not in chat.
4. Unclear tasks are rewritten before work starts. Never start a task you do not understand.
5. Daily reports are non-negotiable. They are how the team stays aligned without constant meetings.