Stephen Covey’s Circles of Influence for Jira, Multiple Jobs, and Freelancers: Exact Steps to Prioritize What You Control

Stephen Covey’s circles of influence separate what you control (your actions), what you influence (your impact on others), and what concerns you (external factors you can’t change). For freelancers, employees with side projects, or anyone managing multiple jobs, this framework eliminates the noise of overlapping deadlines, client demands, and tool sprawl (like Jira issues or GitHub PRs). Here’s how to apply it directly to your workload.

Step 1: Map Your Tasks to the Circles (With Real Examples)

Start by listing every task, issue, or concern across all your jobs. Then assign each to one of the three circles. Use these questions to classify:

• Circle of Control (100% yours): Can I complete this without anyone else’s input? Example: Writing code for a feature branch, blocking 2 hours for deep work, or updating your portfolio.
• Circle of Influence (conditional): Does this depend on someone else’s action, but I can nudge it forward? Example: Following up on a Jira ticket assigned to a teammate, sending a client proposal, or negotiating a deadline.
• Circle of Concern (no control): Is this entirely outside my power? Example: A client’s budget cut, a teammate’s sick leave, or a GitHub PR stuck in review.

Example for a freelance developer with 3 jobs:

• Job 1 (Startup): Circle of Control – "Implement login API endpoint" (you code it). Circle of Influence – "Get client feedback on wireframes" (you send them, but they must respond). Circle of Concern – "Startup’s funding round might fail" (no action possible).
• Job 2 (Agency): Circle of Control – "Fix CSS bugs in the staging environment" (you deploy the fix). Circle of Influence – "Clarify requirements with the PM" (you ask, but they must answer). Circle of Concern – "Agency’s QA team is understaffed" (you can’t hire for them).
• Job 3 (Side Project): Circle of Control – "Write blog post draft" (you write it). Circle of Influence – "Ask a friend to review the draft" (you ask, but they must reply). Circle of Concern – "Algorithm change might tank my traffic" (no control).

Step 2: Shrink Your Circle of Concern (Exact Tactics)

You can’t eliminate concerns, but you can reduce their impact with indirect actions. Here’s how to move items from "concern" to "influence" or "control":

• For Jira/GitHub issues: If a ticket is blocked by a teammate (concern), add a comment with a deadline: "@teammate, can you review by EOD? If not, I’ll escalate to [manager]" (now it’s influence).
• For clients: If a client’s indecision is delaying a project (concern), send a message: "I’ll proceed with Option A by [date] unless I hear otherwise" (now it’s influence).
• For tools: If you’re drowning in notifications (concern), mute non-critical Slack channels or set up filters in Jira to only show tickets assigned to you (now it’s control).

Step 3: Prioritize Within the Circle of Influence (Using Eisenhower + Covey)

Combine Covey’s circles with the Eisenhower Matrix to sort tasks by urgency and importance. Label each task in your circle of influence with one of these four quadrants:

• Urgent + Important (Do now): A Jira ticket due today that blocks your team. A client deliverable with a hard deadline.
• Not Urgent + Important (Schedule): Learning a new framework to improve future work. Writing documentation for a project.
• Urgent + Not Important (Delegate or batch): Responding to non-critical emails. Attending a meeting where you’re not needed.
• Not Urgent + Not Important (Eliminate): Scrolling LinkedIn for "inspiration." Checking Slack every 5 minutes.

Example for a day with 3 jobs:

• 9:00–11:00 AM: Circle of Control – "Code login API" (Urgent + Important for Job 1).
• 11:30 AM–12:00 PM: Circle of Influence – "Follow up on Jira ticket" (Urgent + Important for Job 2).
• 2:00–3:00 PM: Circle of Control – "Write blog post draft" (Not Urgent + Important for Job 3).
• 4:00–4:30 PM: Circle of Influence – "Batch-respond to client emails" (Urgent + Not Important).

Step 4: Apply This to Jira (or Any Task Manager)

Most task managers (Jira, GitHub, Asana) treat all tasks equally, but Covey’s circles force you to filter by control. Here’s how to adapt Jira:

• Label tasks: Add a custom field (e.g., "Control Level") with values: Control, Influence, Concern. Sort your backlog by Control first.
• Use swimlanes: Create columns for each circle. Move tasks left (Control) or right (Concern) as their status changes.
• Automate: Set up rules to auto-label tasks. Example: If a ticket is assigned to you and has no blockers, label it Control. If it’s assigned to someone else, label it Influence.

Example Jira workflow:

• 1. Morning: Filter your board to show only Control tasks. Work on these first.
• 2. Afternoon: Switch to Influence tasks. Send follow-ups, clarify requirements, or negotiate deadlines.
• 3. End of day: Review Concern tasks. For each, ask: Can I move this to Influence with one action? If not, ignore it.

Step 5: Weekly Review to Keep the Circles Accurate

Your circles change as projects evolve. Conduct a 15-minute weekly review to reclassify tasks:

• Promote concerns to influence: If a client’s budget was a concern but they just signed a new contract, it’s now influence (you can plan work).
• Demote influence to control: If a teammate unblocks a Jira ticket, it moves from influence ("waiting on them") to control ("you can code it").
• Eliminate concerns: If a project gets canceled, archive its tasks instead of letting them clutter your list.

How to Handle Overlaps Between Jobs (Exact System)

When tasks from multiple jobs compete for your time, use this decision tree:

• 1. Is this in my circle of control? If yes, do it now (highest priority).
• 2. If it’s influence: Can I delegate or batch it? Example: Batch client emails into one 30-minute slot instead of responding ad-hoc.
• 3. If it’s concern: Can I turn it into influence with one action? Example: If a client’s silence is a concern, send a deadline-driven message to force a response.
• 4. If no to all: Ignore it. Example: A teammate’s sick leave is a concern, but you can’t cover their work—focus on your own tasks.

Example for a freelancer with 2 client deadlines on the same day:

• Client A: Circle of Control – "Finalize homepage design" (Urgent + Important). Action: Block 3 hours to finish it.
• Client B: Circle of Influence – "Get feedback on wireframes" (Urgent + Important). Action: Send a message: "I’ll assume approval by EOD if I don’t hear back."
• Client C: Circle of Concern – "Their project might get canceled." Action: Note it, but don’t act until they confirm.

Tools to Implement This (Without Switching Apps)

You don’t need to abandon Jira or GitHub. Use these tactics to overlay Covey’s circles on your existing tools:

• Color-code tasks: Assign a color to each circle (e.g., green = Control, yellow = Influence, red = Concern). In Jira, use labels or priority flags. In Foco, each job has a color, making it easy to spot which tasks are yours to control. Learn how to separate contexts without losing the big picture.
• Time-block for control tasks: Schedule 2–3 hour blocks for Control tasks first. Example: 9–12 AM for coding (Control), 2–3 PM for follow-ups (Influence). See how to avoid overlaps with time blocking.
• Automate capture: Use voice notes or email to log tasks quickly. In Foco, dictate a task like "Follow up with client X on the proposal by Friday"—it’ll auto-detect the deadline and priority, turning a concern into an actionable task. For Jira users, Foco’s Plus plan connects to your board and pulls assigned tickets into your Influence circle. Unify tasks from multiple apps without migrating data.

Common Mistakes (And How to Fix Them)

• Mistake 1: Treating influence as control. Example: Assuming a client will approve your proposal just because you sent it. Fix: Add a follow-up task to your Influence list with a deadline.
• Mistake 2: Ignoring concerns entirely. Example: Dismissing a client’s financial troubles as "not my problem." Fix: Add a preventive action, like requesting an upfront payment for the next project.
• Mistake 3: Letting influence tasks pile up. Example: 10 Jira tickets waiting on teammates. Fix: Batch follow-ups into one 30-minute slot per day.

How to Use Foco to Apply Covey’s Circles

Foco’s structure mirrors Covey’s circles, making it easy to focus on what you control. Here’s how:

• Panorama mode: See all tasks from every job, each with its job’s color. Tasks in your Circle of Control (e.g., "Write blog post") stand out because they’re fully yours. Tasks in Influence (e.g., "Get client feedback") are tied to external actions, while Concern tasks (e.g., "Client might cancel") can be logged but ignored until they become actionable.
• Focus mode: Select one job to filter the board. This isolates your Circle of Control tasks for that project, removing distractions from other jobs or concerns. For example, if you’re working on a startup project, you’ll only see tasks you can complete without input from others.
• Voice capture: Dictate a task like "Follow up with the PM on the Jira ticket by Thursday." Foco transcribes it, detects the deadline, and assigns it to your Influence list. With the Plus plan, use Ráfaga to dictate multiple tasks at once—ideal for when you’re juggling concerns from multiple jobs and need to turn them into actionable items quickly.
• Integrations: Connect Foco to Jira, GitHub, or Asana to pull in tasks assigned to you. Set the work destination to "Automatic," and Foco’s AI will sort them into the right job. If a Jira ticket is assigned to you and unblocked, it’ll appear in your Circle of Control. If it’s waiting on someone else, it’ll go to Influence.