Please ensure Javascript is enabled for purposes of website accessibility


EP 185: The New Team Klinck BADA$$ Project Management Plan

December 1, 2020 Emberly Team

Every business needs processes to manage projects and tasks. But this is a place where many entrepreneurs get stuck. That’s why I’m sharing our project planning method and cycle so that you can get a peek into how Team Klinck works.

In case you haven’t heard, I can be a little bit difficult to control when it comes to projects. That’s why we created a system to help keep me in check. We were also trying to create a system that works for us since, unlike many online businesses, we don’t do traditional launches.

Today, I’m going to break down what we’re doing and the model we’ve implemented. But this exact system might not work for your business. The important thing is that you create something that works for you and make changes when necessary.

What You'll Learn in Today's Episode

  • How we mixed different project management theories
  • The questions we asked ourselves about how we want to balance different interests and responsibilities
  • The 3 categories we created for work
    • Projects
    • Rogue tasks
    • Recurring tasks (batchable vs. non-batchable)
  • The other guidelines we created
    • We only work on one project at a time as a team
    • We don’t limit our projects to revenue generating
    • We build extra time into projects and sprints so we have a cushion
    • When someone is working on a project, they’re not working on non-batchable recurring projects
    • Each person will clear the deck of batchable recurring tasks before starting a new project so they have full capacity
    • When you’re not working on a task, you attend to rogue tasks and take a rest
  • The 3 project types we created
    • Major projects–promotions, live events, evergreening a funnel, creating a new product, redoing our tech stack
    • Product enhancements–thinking about how we improve existing products
    • Internal improvements–internal team work, wikis, systems
  • Why we created a project backlog and a system for how it should rank (impact, time, effort, readiness, cost) and reassess it regularly
  • How we implemented a Planning Cycle
    • Start with a debrief (looking back at the last project cycle)
    • Assess whether we need to change the project backlog
    • Plan what’s going to happen with projects (major, enhancement, and internal) and who is actively involved
  • Why we’re not limiting ourselves to quarters and instead are operating on cycles.
  • Why even if this system doesn’t work for you, you need to find something that does.