Manage Consensus HK Campaign until 18Feb

[minhyeong112]

Time Estimate

• I have added a time estimate label

Background Information

The Consensus HK campaign, kicked off in #114, needs:

• Regular check-ins on nReach, SmartLead, and HeyReach to keep up with potential leads.
• Keeping everything organized in HubSpot for accurate lead tracking.
• Tweaking our messaging as we learn what works best.
• Trying out new tools like OpenQ to discover more attendees.
• Chatting with leads to move them through our deal stages.
• Other tasks as they come up to ensure the campaign's success.

I've been handling these tasks and am now putting together this proposal to use UbiquityOS as it's meant to be used. From now on, with our marketing tech stack up and running, I'll create proposals for each campaign, covering everything from start to finish.

Completion Criteria

• Goal: book at least 2 warm lead appointments per day at Consensus HK

Relevant Links

Meet Ubiquity at Consensus Hong Kong

[0x4007]

Non code tasks is a bit more experimental territory but generally a long time label a sign that the task should be broken down more granularly to use time estimates that are like a day or less. Are you able to make more detailed sub tasks?

Our system supports the concept of "parent issues" by linking a checklist of other issues in the specification.

• Link to issue one
• Etc

[minhyeong112]

how about this general framework for "recurring non code tasks"

• "Launch" issue: (usually <1 day) e.g. Consensus HK campaign #114

• "Manage" parent issue (usually <1 hour per day for every day leading up to "the thing") e.g. "manage ConsensusHK outreach everyday for 10 days:

  • "child issue 1" Managing ConsensusHK outreach day 1 (<1 hour)
  • "child issue 1" Managing ConsensusHK outreach day 2 (<1 hour)
  • "child issue 1" Managing ConsensusHK outreach day 3 (<1 hour)
  • "child issue 1" Managing ConsensusHK outreach day 4 (<1 hour)
    .....
  • "child issue 1" Managing ConsensusHK outreach day 10 (<1 hour)

[0x4007]

Seems more precise but also an hour of daily management seems eyebrow raising. Why don't you automate that?

[minhyeong112]

refined proposed framework below. just trying to standardize how we do this since outreach will be a recurring thing

• "Launch" issue: (usually <1 day) e.g. Consensus HK campaign #114

• "Follow up" parent issue (usually <15 min per day for every day leading up to the thing)

  • child issue: ConsensusHK follow up day 1 (<15min)
  • child issue: ConsensusHK follow up day 2 (<15min)
  • child issue: ConsensusHK follow up day 3 (<15min)
  • child issue: ConsensusHK follow up day 4 (<15min)
  • .....
  • child issue: ConsensusHK follow up day 10 (<15min)

• "Adjust" parent issue (usually <2 hours per week for every week leading up to "the thing") this would cover, adjusting copy, finding new leads, linking up with nReach staff, fixing integrations that don't work properly, basically anything to keep the outreach machine running

  • child issue: ConsensusHK follow up week 1 (<2 hours)
  • child issue: ConsensusHK follow up week 2 (<2 hours)

[0x4007]

I would probably batch the follow ups in one task but the rest looks pretty good I think.

[minhyeong112]

batch the follow ups in one task

if I aggregate all the 15 min follow-ups, it would probably be a <4 hour task (15 min/day over the course of ~2 weeks)
the problem here would be if I "/start" a <4 hour task, ubiquityOS will unassign me before the 2 weeks are up

Non code tasks is a bit more experimental territory

in case it's not obvious, I'm only being nitpicky in the spirit of the "experiment" with non code tasks

[0x4007]

Okay then let's try your suggestion. When you make a checklist in a spec, the GitHub webapp UI will allow you to hover over and generate new child issues with a single mouse click.