Setting Joint Goals With Partners for Shared Growth - Blog & Tips

Shared growth depends on goals built with partners, not handed down to them. Setting joint goals with partners works best when the objectives reflect sector realities, clarify each party’s contribution, and define how progress will be measured. CISA is working to develop sector-specific goals for each of the 16 U.S. critical infrastructure sectors, with its first goals developed in partnership with Sector Risk Management Agencies (SRMAs) and sector stakeholders.

Partners may agree on a broad outcome but differ on priorities, capabilities, and what success means. Without a shared framework, goals can be too vague to guide investment or too disconnected from each organization’s role to sustain commitment.

This article explains how sector-specific goals can be developed collaboratively, then translated into SMART objectives that are specific, measurable, achievable, relevant, and time-bounded. You’ll also learn how to balance challenging targets with realistic capacity, connect near-term milestones to long-term progress, and establish clear measures so partners can review performance and adjust their work together.

Joint development of sector-specific goals with SRMAs and stakeholders

Sector-specific goals translate shared risks into coordinated priorities for partners. CISA’s work across 16 critical infrastructure sectors shows why goals need input from organizations that understand each sector’s risks and capabilities.

Aligning Different Priorities

Aligning priorities means turning partners’ distinct needs into outcomes they can pursue together. It matters because a common goal must reflect operational realities, not just broad agreement. Start by listing each partner’s risks, obligations, and available resources, then identify overlaps and trade-offs. For example, one stakeholder may prioritize resilience while another focuses on incident response; both can contribute to a shared risk-reduction outcome.

Sector-specific input makes those choices more grounded. CISA developed its first sector-specific goals with Sector Risk Management Agencies (SRMAs) and sector stakeholders. In February 2024, the National Association of Regulatory Utility Commissioners and the U.S. Department of Energy co-developed cybersecurity baselines for electric distribution systems and connected distributed energy resources. The United Nations says more than 178 countries adopted Agenda 21 at the Earth Summit in Rio de Janeiro, Brazil, in 1992, an example of broad collaboration around shared priorities.

Creating a Shared Goal Plan

A shared goal plan records the outcome, rationale, measures, and decisions partners agree to use. Define the common problem, describe the desired result in plain language, and identify the evidence that will show progress. Then connect each objective to sector needs and partner capabilities. This makes setting joint goals with partners a concrete planning process, not an exchange of general intentions.

Document assumptions and decision rights alongside the goal. For example, a cross-sector cybersecurity plan can distinguish the shared outcome from each organization’s chosen actions, while using agreed baseline measures to compare progress. Keep the plan practical: record the goal, measures, responsible parties, dependencies, and review triggers in one shared reference. If partners disagree on wording, clarify its meaning before approving the measure so everyone evaluates the same result.

Dividing Responsibilities and Tracking Progress

Dividing responsibilities means assigning each action to an accountable partner and identifying dependencies between contributions. Name a lead for every deliverable, supporting organizations, and the evidence each will provide. This prevents shared ownership from becoming unclear ownership. For example, an SRMA might coordinate sector input while stakeholders provide operational information relevant to their activities.

Track progress against agreed indicators, not informal status claims. A shared record can show the baseline, current evidence, owner, blockers, and next decision for each action. Review the same measures across partners and log changes with their rationale. To keep accountability constructive, discuss missed milestones by identifying the cause, adjusting dependencies, and assigning a recovery action. Recognize completed contributions so partners can see how their work advances the shared outcome.

Reviewing Shared Goals

Partners should review goals at planned intervals tied to milestones, risk changes, and the pace of work. The right cadence depends on how quickly conditions change and how soon decisions are needed. Set the schedule when approving the plan, with additional reviews when a major dependency shifts. Regular review keeps measures useful without turning every update into a renegotiation.

Use each meeting to compare evidence with the agreed baseline, confirm owners, and decide whether actions remain relevant. If partners disagree, return to the shared outcome and the criteria used to prioritize it. Record unresolved trade-offs and assign someone to make the decision. Maintain momentum through visible progress, clear commitments, and recognition of contributions. When new evidence changes priorities, revise the plan together and explain how the adjustment affects each partner’s role.

SMART objectives

SMART objectives turn a shared ambition into a commitment partners can define and assess. The criteria are specific, measurable, achievable, relevant, and time-bounded. Researchers do not universally agree that every criterion is essential, so use SMART as a practical test rather than a rigid formula.

Start with specificity. Replace “improve collaboration” with an outcome that names the process, intended change, and partners involved. For example, a manufacturer and distributor could aim to improve the accuracy of shared sales reporting. Clarify which reports matter, what accuracy means to both parties, and which decisions the improved information should support. Clear language reduces the risk that partners agree to the same words but expect different results.

Make the outcome measurable by choosing evidence both sides can access and interpret consistently. One useful measure might be the share of submitted records that meet an agreed completeness standard. Define the data source, reporting method, and how to handle exceptions. If one partner counts records at submission and another counts them after review, their results will not be comparable. Agreeing on the measurement method matters as much as choosing the measure.

Achievability tests whether a target matches partner capacity, dependencies, and current operating conditions. It does not mean choosing the easiest outcome. Identify the people, information, processes, and decisions needed to make progress. A manufacturer and distributor may share an objective, but separate systems or approval workflows could affect delivery. Discuss those constraints before committing, then adjust the scope or sequence so the objective remains demanding and feasible.

Relevance connects an objective to a shared business priority and each partner’s role. Ask which decision or operational outcome the goal supports, and why both parties should contribute. If an objective benefits one organization while creating work for another, address the imbalance directly. Partners can revise the scope, clarify reciprocal value, or agree on an enabling action that makes participation worthwhile. Relevance keeps the objective tied to actual priorities.

Time-bounding gives partners a point at which to evaluate results and decide what follows. Choose a deadline or review period that reflects the work’s dependencies, rather than picking a date without considering the process. Then combine all five criteria in one written objective. For instance, specify the reporting process, shared measure, feasibility conditions, business purpose, and review date. This concise statement gives partners a common reference for discussions and progress updates.

Before approval, read the objective from each partner’s perspective. Can both parties explain the outcome, evidence, responsibilities, and timing in the same way? If not, revise the wording or measurement before work begins. A SMART objective should guide decisions, show where coordination is needed, and make progress assessable without relying on assumptions.

Short-term and long-term goals

Long-term goals define the shared outcome; short-term goals turn it into coordinated work. Partners need both because an ambitious destination cannot guide daily decisions without intermediate progress markers. Conversely, immediate tasks can consume attention without advancing a meaningful outcome. Connect each near-term action to the result partners ultimately want, and make that connection visible in the plan.

Start by describing the long-term outcome in terms both organizations value. For example, a manufacturer and distributor might want more reliable shared sales information for planning. That ambition gives the partnership direction, but it does not show what either party should do next. Break it into connected milestones, such as agreeing on data definitions, improving submission workflows, and using consistent information in planning discussions. Each milestone should produce something that enables the next.

Leo Babauta describes setting one or three goals for the year, then creating sub-goals for each month and action steps for each week and day. This illustrates how a larger objective can be translated into successive layers of work. Partners can use the same principle without copying that exact schedule: clarify the outcome, identify meaningful intermediate results, then assign activities that advance them. The key is making the connection between intention and action visible.

Short-term goals should focus on progress partners can observe and influence. A shared reporting objective could begin with agreeing on field definitions, then move toward consistent submissions, and later support joint analysis. These stages create decision points. If definitions remain disputed, partners can resolve that issue before assessing submission quality. If the data becomes consistent, they can decide whether it supports the longer-term planning outcome.

Long-term goals also need room for learning. Partner capabilities, business priorities, and dependencies can shift as work develops. Preserve the intended outcome, but review whether the route still makes sense. If a milestone no longer supports the outcome, replace it with a more relevant step and record why. This prevents completed activities from being mistaken for progress when the actual result remains out of reach.

Make the connection between time horizons explicit in the shared plan. For each long-term result, identify the current milestone, the action that advances it, and the evidence partners will review. Distinguish a completed task from an achieved outcome. A submitted report is an activity; usable information for a shared decision is closer to the intended result. This distinction helps partners focus on progress, not activity alone.

During reviews, ask whether each short-term commitment still advances the long-term objective. If it does, confirm the next owner and dependency. If not, revise the sequence or clarify the outcome. Partners gain a practical planning rhythm: maintain direction with long-term goals, use near-term work to test progress, and adjust actions when evidence points to a better path.

Specific and challenging goals

A goal should define the result clearly and stretch partners beyond routine performance. “Improve coordination” gives teams no shared target; “reduce errors in shared sales records” identifies a result they can assess. Specificity focuses attention on relevant actions, while challenge gives partners a reason to sustain effort. The target must still account for capability, resources, and the work required from each organization.

Locke and Latham recommend selecting goals within the 90th percentile of difficulty, based on the average prior performance of people who have performed the task. For a partnership, that offers a reference point, not a universal quota. Examine prior results for the relevant work, then choose an ambitious target that stretches performance while remaining within the partners’ capacity. If the partners lack comparable records, first establish a shared baseline.

Make the target specific enough to guide decisions. Name the process, expected outcome, and evidence that will demonstrate progress. For example, a manufacturer and distributor could aim to improve the completeness of shared product records. They would need to define which records count, what “complete” means, and how both parties will assess the result. Without those definitions, each organization could report success using different criteria.

Difficulty alone will not improve performance. Specific, difficult goals are associated with higher performance than easy goals or “do your best” instructions when people receive progress feedback, remain committed, and have the necessary capability. Pair a demanding target with useful feedback and a clear view of each partner’s contribution. If a partner cannot influence the measure, revisit its responsibilities or choose a result within its control.

Challenge can also increase persistence, and difficult goals can prolong effort. That makes ongoing feedback essential: it helps partners distinguish a temporary obstacle from a target that needs revision. For example, if shared records remain incomplete, identify whether the barrier is inconsistent definitions, delayed submissions, or unclear ownership. Agree on a corrective action before lowering the objective. This keeps accountability focused on solving the constraint.

Before approval, ask each partner to explain the target, the evidence, and the effort required. If their interpretations differ, clarify the wording and responsibilities. Then compare the proposed challenge with prior performance and available capabilities. A sound joint goal should stretch the partnership, connect to a meaningful outcome, and give both parties a credible path to progress. Review the evidence together and adjust the approach when it reveals a real barrier.

One useful check is to compare the objective with the SMART framework: specific, measurable, achievable, relevant, and time-bounded. Researchers do not universally agree that these criteria are necessary, so treat them as a prompt for discussion rather than a pass-or-fail test. Partners can use them to spot missing definitions, unclear evidence, an unrealistic demand, weak connection to shared priorities, or no agreed time boundary, then decide whether clarification would help.

In healthcare, the U.S. Department of Health and Human Services published voluntary healthcare-specific Cybersecurity Performance Goals on January 25. Their voluntary status offers an example of goals that can inform discussion without making every recommendation a required target. Partners can likewise distinguish an agreed performance objective from supporting guidance, and state which measures and responsibilities they have actually committed to.

How to align different priorities when setting goals together

Partners can align priorities by connecting separate business needs to an outcome they both value. A distributor may want more reliable product data, while a manufacturer needs cleaner information for planning. Rather than pushing either priority aside, define the shared result both depend on. This gives discussions a practical focus: what outcome matters, whose needs it serves, and what trade-offs it requires.

Begin by asking each partner to name its desired result, operational constraint, and reason for participating. Then distinguish shared outcomes from individual preferences. For example, both organizations may need accurate sales records, although one prioritizes faster reporting and the other fewer corrections. The shared goal can address record quality, while supporting actions reflect each partner’s workflow and capacity.

Compare priorities against agreed criteria before choosing a goal. Useful criteria include alignment with strategic outcomes, urgency, partner influence, resource demands, and dependencies. A manufacturer and distributor might find that a data-quality objective supports both planning and reporting, while a new reporting format mainly serves one team. That distinction does not automatically rule out the format, but clarifies whether it belongs in the shared goal or a partner-specific workstream.

Make trade-offs visible in a simple decision record. For each proposed goal, note the expected benefit for each partner, the effort required, dependencies, and consequences of delay. If one organization must change its workflow while the other receives most of the immediate benefit, discuss a reciprocal contribution. That might involve sharing expertise, aligning data definitions, or taking responsibility for a dependent task. Explicit exchanges reduce the risk of hidden expectations turning into disputes.

When partners disagree, return to the evidence and intended outcome. Ask each party to explain which operational need supports its preferred goal, then identify facts both sides accept. For instance, if the disagreement is about reporting speed versus data accuracy, examine how each option affects decisions and downstream processes. If evidence remains inconclusive, agree on a limited test with a defined measure and review point. The test should answer the disputed question, not add unrelated work.

Record the final decision in language each partner can explain consistently. Include the shared outcome, individual contributions, accepted trade-offs, and conditions that would prompt reconsideration. A brief decision log preserves context when team members change or priorities shift. During the next review, compare actual progress with the agreed rationale, then keep, revise, or retire the goal based on its continuing value to both organizations.

For teams coordinating partner priorities and shared workflows, explore a structured approach to partner goal coordination.

CISA’s Cross-Sector Cybersecurity Performance Goals 2.0 align with the NIST Cybersecurity Framework 2.0.

Leo Babauta recommends allowing yourself to plan when needed while gradually letting go of the habit of planning.

Computer Market Research: PartnerPortal™

Computer Market Research offers PartnerPortal™ to help organizations coordinate channel partner programs and performance. The platform centralizes partner onboarding, deal registration, and performance tracking, giving teams a shared foundation for managing partner activity. When joint goals depend on clearer program administration, Co-op/MDF Management and Rebates & Incentives support related channel processes.

Consider this approach when partner information is fragmented across manual workflows or teams need consistent visibility into program activity. Centralized administration can make it easier to review partner participation against agreed objectives and identify where follow-up is needed. To discuss how PartnerPortal™ may fit your partner program, contact Computer Market Research.

Put the next shared objective into motion

Choose one partner outcome that can guide a real operational decision as your next step. Use it to focus a working conversation: what result matters now, what evidence will show progress, and which teams need to contribute? A clear starting point helps turn alignment into coordinated work without adding another disconnected initiative.

For channel programs, Computer Market Research’s Co-op/MDF Management and Rebates & Incentives support the administration of partner funding and incentive processes. These offerings are relevant when shared objectives involve those workflows. A disciplined approach to setting joint goals with partners also gives teams a consistent basis for reviewing responsibilities and adjusting actions as priorities evolve.

Choose an objective your partners can act on, document the first commitment, and bring the right stakeholders into the discussion. If you’re ready to explore how Computer Market Research can support your partner program, contact Computer Market Research. A focused next step can help your partnership turn shared intent into progress.