Improving Team Productivity: Goals, Planning and Focus
Productivity improves when people choose work that matters, not simply when they stay busy. In a conversation between Nathan Gilmore and Brett Harned, the focus is on a practical rhythm: define quarterly goals, turn them into detailed plans, check workloads, and review progress every week.
Episode metadata
Episode details: Time Limit podcast, 47 episodes. Episode 43, Season 2, published 2020-11-12. Duration shown in the player: 43:31 (structured data lists PT43M32S). Playback is provided through the audio/play control referenced by the form-controls-contract module; live playback has not been verified.
A practical goal-to-plan rhythm
Start with the result you want, then work backwards. A useful sequence is: set a quarterly goal for each team, break it into a plan covering at least the next month, identify the single most important task for today, and check whether workloads leave room to do that work well. Reviewing the goal weekly keeps the plan connected to daily choices and makes drift visible early.
This episode covers simple strategies to increase productivity for yourself and your team, why having a plan is an easy way to improve team productivity, and how goal-setting connects to team performance. In other words, clear goals are not paperwork separate from performance; they are the mechanism that tells people which work matters, so effort is directed where it counts.
A simple weekly checklist:
- Confirm the quarterly goal still reflects the right priority.
- Review planned work for the coming month and the next few weeks.
- Check each person's workload for overload or gaps.
- Name the one important task that matters most today.
- Note anything that is slowing progress and decide what to remove, delay or support.
Busy is not the same as progress
Busy work can create the appearance of progress while goals barely move. The distinction is whether completed tasks advance a meaningful outcome. If a to-do list is full but the quarterly goal is unchanged, the problem may be selection rather than effort. Step back from individual tasks and ask what the organisation, the team and each person need to accomplish, including life outside work.
Handling a productivity problem without comparison
When someone falls behind, compare progress with the plan and baseline rather than with colleagues. A repeated pattern is a signal to investigate, not a reason to rank people. Ask what is going on, what has changed, and whether the workload, priorities or support need adjustment. That approach turns a productivity concern into a problem-solving conversation.
Example: testing a shorter week before committing
The episode describes a move that began as half-day Fridays tested over two summers and later became a four-day week. Work was completed and morale rose. Use that as an example of testing a change before making it permanent: define what success looks like, run it for a bounded period, review output and morale, and only then decide whether to continue.
Small teams and fewer meetings
Larger groups can dilute accountability and make coordination harder. Keeping teams to two or three people is presented as a way to strengthen ownership. Meetings deserve the same scrutiny: if a short email can deliver the information and decision needed, replace the meeting. Fewer unnecessary meetings protect time for the work the plan is meant to deliver.
Frequently asked questions
How do you motivate a team and increase productivity?
Begin by looking beyond daily tasks to the outcomes you want at company, team and personal levels. Then choose work that advances those outcomes, set quarterly team goals, plan at least a month ahead in detail, check workloads, and review the goals weekly.
How should a manager handle someone who falls behind?
Use the plan and baselines to spot a pattern first. Then ask what is happening and what support or change is needed, rather than comparing one person with another.
What happened when the schedule changed to four days?
The discussion describes testing half-day Fridays over two summers before moving to a four-day week. Work continued to be completed while morale improved, and retention was also discussed as a benefit.
Why keep teams small and cut meetings?
Keep teams to two or three people where possible and remove meetings that could be handled by email. Smaller groups and fewer unnecessary meetings are presented as ways to protect focus.