How to Track Coaching Client Goals Without Strides

You can track coaching client goals without Strides by defining the difference the client wants, choosing evidence that fits it and reviewing a manageable next action. A shared coaching workspace can bring those records closer to sessions, but the tool should support the goal rather than make progress look more certain than it is.

Strides supports habits, targets, averages and projects. Its current official site also describes inviting accountability partners and working on a goal together, with an Apple-device/iCloud qualification for that collaboration. A coaching alternative therefore needs a useful reason beyond claiming that Strides cannot share progress. A client who finds the existing app helpful may keep it. This guide explains when a shared coaching workflow helps and what to do when a progress bar conceals the real situation. See the official Strides features for its current options.

A personal goal tracker vs a shared coaching goal workflow

A personal tracker can support a client’s own monitoring. A shared workspace can make agreed goals and follow-up easier to discuss with a coach. The right choice depends on what should be shared, how often it will be reviewed and what the client will actually use.

Coachful is our #1 recommendation when the practical need is to discuss a goal alongside coaching sessions, linked actions and reflections. We build it, so this is a maker’s recommendation for this workflow, not a measured ranking of every tracker. Its Daily momentum view counts linked tasks and scheduled habits; those counts do not establish that a client achieved a business outcome. Review available fields, permissions and progress behavior before promising an OKR hierarchy, automatic outcome measurement or sponsor dashboard.

Strides may remain the better choice for someone who mainly wants a personal pace line or an established logging routine. A brief summary brought to coaching can connect the two without migrating years of private history. Choose the smallest change that solves a demonstrated problem.

Completing the task does not establish the outcome. Keep these records connected without making them interchangeable. A beautiful progress display is useful only when its meaning is clear.

Why goal tracking can become unhelpful

A goal may be too broad, outside the client’s control or defined mainly to satisfy a sponsor. Ask why it matters and whose goal it is. A person may need to negotiate expectations before they can make a meaningful commitment.

Tracking can also become extra work. If the client already records information in an appropriate system, a short summary may be enough for coaching. Requiring duplicate entries can reduce the quality of the conversation while creating an apparently fuller dashboard.

Avoid explaining an incomplete milestone as hidden resistance without evidence. The issue might be unclear authority, a dependency, workload or a revised priority. Ask what happened before interpreting the status.

Our goal-setting worksheet for coaches can help structure the initial inquiry. Use the framework to make a goal clearer, not to force every meaningful change into the same numerical format. For ongoing reviews, the progress-tracker templates offer a separate way to organize evidence and uncertainty.

There is research behind monitoring, but it does not validate any particular dashboard. Harkin and colleagues’ 2016 meta-analysis included 138 studies and 19,951 participants and found an average improvement in goal attainment from monitoring interventions. Almost all included studies concerned health. Monitoring frequency and attainment had to be distinct measures. That supports asking whether tracking helps; it does not establish an executive-coaching effect size, prove that task completions are outcomes or require clients to make private progress public.

Define the goal and useful milestones

Start with a concrete description of improvement. Who would notice what, in which situation? The client may want to lead meetings that end with a clear decision and owner. That description can guide evidence without claiming every meeting can be reduced to a score.

Choose a small number of milestones that represent real progress. For the meeting goal, the client might clarify decision authority, introduce a brief and review several examples. Avoid creating ten tasks merely because the system has space for them.

Separate influence from control. A client can prepare a clearer brief, but cannot guarantee every participant agrees. Include requests or dependencies where another person’s action is needed. A goal plan should not make the client accountable for outcomes they cannot determine alone.

Set a review date and define what will count as useful evidence. A task list can show reported completion; an outcome may need examples, appropriate feedback or operational information. Explain what a progress percentage represents if you use one.

Illustrative dialogue: a stalled milestone

Consider a fictional vice president, Rowan, working with coach Leena. Before their new review period, Rowan has completed a course, attended four preparation sessions and submitted a worksheet. Those are six completed preparation activities, not six demonstrations that team decision ownership improved. At their 3 November 2026 session, the delegation milestone is still open. The eight-turn exchange below illustrates investigating the situation rather than reading a personality trait into an overdue item.

Coach: The decision-boundary milestone is still open. What happened?

Client: I drafted it, but the chief operating officer has not agreed which decisions can move.

Coach: Then which part is complete, and which part depends on someone else?

Client: The draft is complete. Approval is pending.

Coach: What is the useful next action?

Client: Ask for a decision on two specific categories, with the risks explained, rather than send the whole document again.

Coach: How should the record show that?

Client: The draft task is done, the approval dependency stays open and the goal is still in progress.

This is a more accurate account than marking the entire goal failed or complete. It also gives the next session a useful question. The display should follow the work, rather than force the work into one ambiguous label.

If the dependency cannot be resolved, the client may need another route, a revised goal or a decision that the original milestone is no longer worthwhile. Keeping an obsolete task overdue indefinitely does not improve accountability.

Rowan’s chief operating officer, Felix, has genuine decision authority. On 9 November Felix approves delegation within two routine purchasing categories below €2,000, while retaining the existing risk-escalation requirements. This is narrower than Rowan’s original request. Leena helps Rowan describe the approved scope accurately; she cannot extend Felix’s authorization or treat an unanswered request as consent. Rowan declines Leena’s suggestion to add a daily leadership score. A short review of actual decisions will be more useful.

Reviewing progress without misleading percentages

Ask what a percentage means. It might represent completed milestones, a client’s self-rating or a system calculation. Those are different forms of information. State the basis rather than implying the number is an objective measure of leadership development.

Use qualitative evidence where appropriate. A client may describe how they handled a particular disagreement, what feedback they received and what they would change. Keep the account specific and distinguish the client’s interpretation from another person’s actual words.

Look for unwanted effects. A goal to reduce escalations could discourage people from raising legitimate risks. A goal to speak more could crowd out listening. Review whether the measure is serving the intended purpose rather than rewarding the easiest visible behavior.

At each review, decide whether to continue, adjust or stop. A changed business priority can justify retiring a goal. Explain the decision in the record instead of preserving an impressive but irrelevant plan.

In Coachful, inspect the goal’s actual path before interpreting its percentage. Milestone weights can determine progress. A declared finish-line milestone, or the relevant Program or Journey path, can also affect completion; completing a personal path without a declared finish line is a different case. Linked daily tasks are another display again. None of those mechanisms independently checks whether a chief operating officer approved a new authority boundary. Keep that evidence explicit in the review instead of changing a number to make the story convenient.

A demonstration below shows three of seven daily linked actions done. That is three tasks plus four habits in that view, with three completions across them. It is not three of seven leadership goals, a 43% delegation outcome or a clinical measure. Historical check-ins and a current-day count also use different periods. Read the label before borrowing a number for a report.

Worked case: the progress bar is full but the goal is not met

A client completes a course, attends four sessions and submits a worksheet. The plan shows every task complete, yet the team still lacks clarity about decision ownership. The completed work may have value, but it has not established the desired outcome.

Ask which task was expected to create the difference and what happened when the client applied it. Perhaps the worksheet never led to a team conversation, or the team conversation revealed conflicting authority. That gives you a more useful next step than adding another course.

Revise the plan to separate learning activities from application and outcome evidence. Keep the completed tasks accurate, but do not use their total as proof the broader goal is achieved. A clear note can explain what remains to be tested.

This distinction also matters in sponsor reporting. Attendance, activity and results should not be presented as the same thing. Agree appropriate reporting and avoid sharing private reflections simply to make a progress report look more convincing.

Rowan and Leena examine eight selected decision records from 10–20 November. Five concern routine decisions: four have a clear team owner within the approved scope, while one remains unresolved because its exception falls outside it. Three concern risks: two were raised through the required route, but one was withheld because a manager thought the goal meant reducing escalations of every kind. These are eight selected records, not the complete volume of work or a representative organizational survey.

Leena initially says, “Four of five means the delegation goal is 80% achieved.” Rowan objects: that leaves out the withheld risk and treats a selected sample as the whole goal. Leena withdraws the statement. Four of five describes only the routine-decision subset. She apologizes for overstating it and removes the proposed achievement claim from the unsent sponsor summary. The correction does not erase the four useful decisions or the manager’s real misunderstanding.

Rowan addresses the withheld risk through the organization’s existing process. Coaching is not a substitute for that procedure. The useful revision is to distinguish routine ownership from timely risk escalation, rather than reward a lower total message count. Rowan chooses one clarification for the team and a separate exception question for Felix. Leena does not prescribe the operational response or interview colleagues without agreement.

They review these records during their 35-minute session on 23 November, from 09:00 to 09:35 UTC. The summary deadline has already been missed. Before the summary is sent, Rowan approves only the scope already authorized on 9 November, the two evidence subsets and the unresolved exception. Rowan refuses to share private reflections about feeling unsupported. The agreed delivery deadline was 20 November at 12:00 UTC. Leena actually sends the approved summary on 23 November at 10:00 UTC, 70 elapsed hours late, including the weekend. She acknowledges the miss instead of changing the due date. Felix replies at 14:00 that the exception is under review. Receipt and review do not approve the requested extension of authority.

Step-by-step rollout in a coaching relationship

Agree one goal and the minimum record needed to review it. Explain who can see the information and when you will look at it. Do not let a dashboard imply continuous monitoring or urgent support unless that is explicitly arranged and deliverable.

Configure the goal and next action using the actual available tools. Keep the wording client-owned. A sophisticated framework is unnecessary if a simple milestone and a clear review question do the job.

If moving from Strides or another tracker, transfer only the relevant history and avoid duplicate logging. Do not promise a direct Strides import or preserved streak calculation without testing the actual supported route. The official Strides Help describes notes, editing historical logs and skipping a log, so absence and non-completion also need interpretation. Copying a number without its period, exclusions and meaning can produce a misleading new record.

Rowan keeps personal habits in Strides and brings a selected summary to coaching. Only the agreed delegation goal and useful actions belong in the shared coaching record. There is no requirement to invite Leena as an accountability partner or transfer unrelated health, family or financial entries. If using Coachful journal pages, review the actual per-page sharing controls and any intentional sharing before relying on a privacy assumption. A sponsor reporting agreement is separate from the client’s decision to share a page.

Review after a short trial. Ask whether the record helped the client prepare, notice progress and choose the next action. Simplify or change it if not. The useful outcome is a clearer path, not permanent commitment to the tracker.

Try the record with one goal before moving an entire caseload. Confirm which actions can be linked, which goal is active and what a completed, paused or archived record means in that workspace. Retain the earlier evidence when changing status; do not rewrite old preparation as a new success. Check what the client can actually open and what the intended recipient receives. A coach’s view alone does not prove the client’s access or a sponsor’s authorization.

1. Define the desired difference.
2. Separate goal, milestone, task and evidence.
3. Record dependencies and influence honestly.
4. Review actual effects, not only completions.
5. Adapt the plan as the client learns.

A short preparation sheet for the next session

Ask the client to bring one action attempted, one observation and one decision they want help with. This can be enough to turn a goal record into a useful coaching agenda without requiring a long report.

Where a number is helpful, ask what it represents and what context it misses. Where a story is helpful, ask for the concrete situation and what remains uncertain. Numbers and examples can inform each other.

Close the session with a next step the client can recognize. A well-maintained goal plan should make the next conversation more specific while leaving room for the client to change direction responsibly.

For Rowan, preparation is three short items: the unresolved exception, the clarification about risks and the next decision required from Felix. Leena proposes another weekly form; Rowan declines because it would duplicate the work record. They use the already authorized summary instead. A review needs enough evidence to make a decision, not a new collection habit for its own sake.

Use our performance-audit guide when you need a broader service review. Keep that separate from an individual client’s goal check, especially when costs, attendance and operational outcomes use different denominators.

A goal may need a different measure than the obvious one

A client wants fewer escalations from the team. Counting fewer messages may look like an easy measure, but the number can fall for the wrong reason: people may stop raising genuine risks. Ask what a useful escalation looks like before making reduction the goal.

The preferred difference may be that routine decisions stay with the appropriate owner while important risks arrive early with a recommendation. That requires examples and a clear decision boundary, not only a lower count.

Similarly, a goal to speak more in meetings can improve contribution or crowd out others. A goal to complete preparation can support a better decision or become a ritual unrelated to it. Examine the effect the client wants and the behavior the measure might encourage.

Choose a small evidence set that can distinguish useful progress from an unintended effect. For the escalation goal, review a few routine decisions and a few risks that were raised. Ask what authority, information and support were available. Keep the sample’s limits clear.

The client can retain a numerical target where it genuinely helps, while adding context. A personal tracker may record a count, and the coaching conversation can examine what the count means. There is no need to reject numbers or stories categorically; each should do a clear job.

At the review, ask whether the measure is still serving the goal. If it is rewarding the wrong behavior, revise it openly. A changed measure can reflect better understanding rather than an attempt to avoid accountability.

At the 27 November close, Rowan pauses the broader delegation goal pending Felix’s exception decision, rather than marking it achieved. The preparation remains complete and the new authority scope remains limited. Rowan owns asking for Felix’s decision by 3 December. Its answer and the team’s later behavior are unknown at close. Leena’s coaching ends without another monitoring package, sponsor interview or promise to chase that response.

The bounded review period contains 55 live coaching minutes on 3 November, 35 on 23 November and 25 on 27 November: 115 minutes in total. The four earlier preparation sessions are outside that interval. The 115 also excludes Rowan’s team work, Felix’s review and Leena’s preparation or late summary administration. Recording that boundary prevents a convenient live-session total from becoming a claim about total effort or the cost of achieving the goal.

Frequently asked questions

Is Strides only for simple habit tracking?

No. Its official materials describe habits, targets, averages and projects. A coaching alternative should be chosen for a useful shared workflow, not an inaccurate claim that the app cannot handle goals.

Does completing all tasks mean the goal is achieved?

Not necessarily. Tasks can be preparation or learning activity. Review the intended difference and appropriate evidence separately, and explain what any progress percentage measures.

How many goals should a client track?

Use a manageable set that fits the client’s capacity and priorities. There is no universal ideal count. A single well-defined goal may be more useful than a large board of obligations.

Can sponsors see the goal record?

Only according to the actual permissions and reporting agreement. A sponsor may receive an agreed summary without private reflections. Clarify the arrangement before collecting information.

What if a goal becomes irrelevant?

Review why and decide whether to revise or retire it. Record the decision accurately. Continuing to chase an obsolete milestone is not inherently better accountability.

Goal tracking is useful when it makes the desired difference and next action clearer. Explore Coachful’s goal and coaching tools if you want that record connected with sessions and agreed follow-up.