ClickUp Implementation Consultation — 2026-04-05
Overview
Consultation with Eloiza Serate (Virtual Champions) to finalize the ClickUp implementation go-ahead. The blueprint/audit phase is complete and approved; this meeting scoped the implementation phase, identified the one remaining open decision (task assignee protocol), and established the data migration target window. A separate SOW for implementation will be issued.
Attendees:
- Eloiza Serate — Virtual Champions (external consultant)
- Melissa Cusumano — Asymmetric
- Isalia Ramirez — Asymmetric
Key Decisions
| Decision | Outcome |
|---|---|
| Proceed with implementation? | ✅ Yes — greenlit |
| Audit/blueprint scope vs. implementation scope | Implementation is a new, separate SOW |
| Sales in ClickUp? | ❌ No — sales stays in HubSpot; integration considered only if needed |
| Data migration window | Targeting Thanksgiving weekend, Nov 27–30 (pending Mark's approval) |
| Task assignee / subtask protocol | ⚠️ Still undecided — see open question below |
Open Question: Task Assignee & Subtask Protocol
This is the one unresolved design decision that must be made before or during the build phase.
Option 1: One Assignee per Parent Task
- Pro: Clear workload forecasting; clean capacity view (e.g., "Raphael is fully booked")
- Con: Subtasks can be missed by team members who aren't the named assignee
Option 2: Multiple Assignees on Parent Task
- Pro: All relevant parties see the task in their inbox
- Con: Inbox clutter; task sequence can be obscured when subtasks surface out of order
Potential Mitigations
- Numbered tasks — prefix task names with
01 -,02 -, etc. to enforce visible sequence - Dependencies — use ClickUp dependency chains to block out-of-order execution
- Dynamic subtask creation — subtasks are only created when the parent reaches the relevant status (e.g., a "Review" subtask appears only when status flips to "In Review")
- ⚠️ Trade-off: loses forward workload forecasting visibility
Context: Asymmetric previously used single-assignee + subtasks, then switched to multi-assignee on parent tasks after subtasks were getting missed post-merger growth. Training was identified as the key mitigating factor regardless of which protocol is chosen.
Implementation Scope & Timeline
- Build estimate: ~10 development hours, completable within one week of SOW approval
- Training plan:
- General training for all users (1–3 sessions depending on question volume)
- Advanced/admin training for nominated ClickUp admins (one per team)
- Isalia to nominate admin candidates per team and share names with Eloiza
- Data migration:
- Handled by a specialist migration team (lower rate than implementation team)
- Requires a full 4-day window to avoid operational disruption
- Target: Nov 27–30 (Thanksgiving weekend)
- Challenge: Asymmetric's global team structure means some staff will still be working — Melissa to discuss a team-wide exception with Mark
Finance & Sales Integration
- Finance: Mark currently handles all invoicing. A Friday call with Mark is scheduled to define finance processes and scope what goes into ClickUp. Karen may also be involved.
- Sales: Will remain in HubSpot. A ClickUp↔HubSpot integration will be evaluated only if a need emerges.
Action Items
- [ ] Eloiza — Sync with Elisa on blueprint updates; revise and send new implementation SOW + plan to Melissa and Isalia
- [ ] Isalia — Nominate ClickUp admins per team; share names with Eloiza
- [ ] Isalia — Resend Friday finance call invite to Mark; ask him to manually add a calendar block (auto-decline from focus time blocked the original invite)
- [ ] Melissa — Propose Nov 27–30 migration window to Mark; confirm with Eloiza once approved
Transcript Excerpts
On proceeding with implementation despite open questions:
"Once you see it and it's going to make a bit of sense, and then if there's anything that's still in a gray area, then we can further discuss. But yeah, seeing it visually would answer a lot of questions." — Eloiza Serate
On the assignee protocol history at Asymmetric:
"I used to be a true believer in one person at the top level, and then everybody would be on a subtask… Then we switched it because the subtasks would be getting lost, and people wouldn't see the subtasks. So that's why we started putting everybody in the parent task." — Melissa Cusumano
On the dynamic subtask trade-off:
"If it's like a Gantt chart with all of the tasks listed from top to bottom, then you have a forecast of what the workload looks like in the future… The subtask only gets added, so you lose that hindsight or the forecast ability." — Eloiza Serate
On the migration window:
"It would be great if we can have like the full four days… Maybe just an exception for this year or something, just so we can support the migration and make it a smooth transition." — Eloiza Serate
On sales staying in HubSpot:
"That was one thing that we decided not to really have in the Blueprint was the sales because he wants to stay on HubSpot… Maybe just an integration if needed." — Melissa Cusumano / Eloiza Serate
Related
- [1]
- [2]