You start your week with the best intentions. This is the one—you’re going to knock it out of the park this week. But by Friday, a dozen random tasks pulled your attention away from your goal. Exactly what your goal even was seems very, very hard to remember.
Right? Me too.
Whether you’re wrangling your team to reach a milestone this week or psyching yourself up to launch your course this month, you can ride the primo wave of a supportive process to get there.
In 5 simple steps, here’s what we’re trying at Pathwright right now:
Project planning gets a lot simpler if you set your destination before embarking. If you’re not used to filling out a project brief, just try answering these three questions to set your destination:
The time frame is up to you. We work in six-week project cycles at Pathwright. After trying week-to-week and quarterly, six week chunks works perfectly for us. Your situation may vary, but I recommend not planning too far out.
Since you know your destination, what strategic goal for this week will take you there in time? If you’re planning to launch a new course by the end of the month, then maybe your goal for the first week sounds like “write a set of learning outcomes for my course.”
At Pathwright, we recently tried pushing ourselves to build a prototype the very first week. For a new feature, that meant developing an ugly but testable version. Prototypes shouldn’t look too nice, but they should uncover problems that were invisible before and would have derailed the project later. So maybe your goal for week one is “outline my course in Pathwright.”
For most of us, goals don’t work if we’re the only ones who know them. It’s too easy to downgrade my ambitions or reschedule the deadline. To prevent those outcomes, tell your team your destination and weekly goals.
Cheer with each other when you make it, and figure it out together when you don’t. Shame doesn’t belong here; you need to keep the process supportive, or it won’t work. Everyone misses goals sometimes for all kinds of reasons. Patterns of success are great to build on; patterns of failure are great for encouraging experimentation.
For missed goals, try asking these questions:
For met goals, on to the next step:
Show your work from your weekly goal and tell your team a little about it. I’m surprised by how accessible work way outside my own discipline is—development project, sales initiatives, etc.—after a link and a few sentences of explanation.
A few examples we’ve recently shared:
So far, it seems like if we decide to show and tell about our work every week, anything can be show-and-tell’d. Again, we use Slack for this. It’s amazing to see a digest at the end of the week summarizing the cool things everyone worked on. I think you’ll be pleasantly surprised how amazing your own team is when you share your work every week.
If you’re tired of not being sure your people are learning what they need to, try Pathwright. We built it from the ground up for ultimate clarity—from powerful outlining to seeing actual faces move from one step to the next. Get started free.