Taskspace is an AI-powered EOS (Entrepreneurial Operating System) management platform for ADHD founders, multi-company operators, and leadership teams. It includes EOD reports, quarterly rocks, weekly scorecards, Level 10 meetings, IDS issue boards, and accountability charts — all in one place.

What is EOS (Entrepreneurial Operating System)?

EOS, or the Entrepreneurial Operating System, is a complete business management framework created by Gino Wickman and described in the book 'Traction.' It helps leadership teams clarify, simplify, and achieve their vision using six key components: Vision, People, Data, Issues, Process, and Traction. Taskspace implements the EOS framework digitally.

How much does Taskspace cost?

Taskspace has a free plan for up to 3 team members with 50 AI credits per month. The Team plan is $9/user/month and supports up to 25 members with integrations and 200 AI credits/user/month. The Business plan is $19/user/month and includes unlimited members, unlimited AI, SSO, custom branding, and API access.

What is an EOD report?

An EOD (End-of-Day) report is a daily accountability check-in where team members log what they completed, any blockers they encountered, and their priorities for tomorrow. In Taskspace, EOD reports are submitted via a simple form or Slack prompt, and AI automatically summarizes the team's daily output for leadership.

What are Rocks in EOS?

In EOS, Rocks are your 90-day priorities — the 3–7 most important things that must get done this quarter to move the business forward. The term comes from Stephen Covey's 'big rocks' analogy. Taskspace tracks rocks for every team member, shows progress, and connects rocks to weekly scorecard and L10 meeting reviews.

What is a Level 10 Meeting (L10)?

A Level 10 Meeting is a structured 90-minute weekly team meeting used in EOS. It follows a specific 8-part agenda: segue, scorecard review, rock review, customer and employee headlines, to-do review, IDS (Identify, Discuss, Solve), conclude, and rate the meeting out of 10. Taskspace facilitates L10 meetings with a built-in IDS issue board.

Is Taskspace good for ADHD entrepreneurs?

Yes. Taskspace was specifically designed with ADHD founders in mind. The EOS framework provides consistent external structure (rocks, scorecards, L10 meetings) that supports ADHD brains without rigid processes. EOD reports are designed as brain-dump style check-ins, and the platform uses progressive disclosure to reduce cognitive load.

Can I manage multiple companies in Taskspace?

Yes. Taskspace supports multiple workspaces, which allows multi-company founders to run separate EOS instances for each business from one account. Each workspace is fully isolated with its own team members, rocks, scorecards, and meeting history. Team plan and above support multi-workspace.

The IDS Process: How to Solve Business Issues Permanently

Most leadership teams are terrible at solving problems.

Not because they lack intelligence. Not because they don't care. But because they mistake talking about a problem for solving it.

They spend 45 minutes in a meeting discussing an issue, feel like progress was made, and then watch the same issue appear on the agenda two weeks later. And two weeks after that.

EOS has a name for this: the Issues List. And it has a process for actually clearing it: IDS.

What Does IDS Stand For?

IDS stands for Identify, Discuss, Solve.

It is the three-step problem-solving methodology used in EOS during the Issues Solving Track of a Level 10 Meeting. The entire purpose of IDS is to ensure that when a team sits down to address a problem, they actually resolve it — permanently — rather than just talking around it.

Here is the simplest version:

Identify — What is the real issue?
Discuss — What do we collectively know about this issue?
Solve — What is the specific action or decision that will resolve it?

Simple. But most teams skip step one entirely, conflate steps one and two, and never actually reach step three.

Why Most Teams Fail at Problem-Solving

The core failure is this: teams discuss symptoms instead of root causes.

A team member raises an issue: "Our customer onboarding is a mess." The team immediately jumps into discussing onboarding. They share war stories, opinions, and anecdotes. Forty minutes later, they have a long list of everything wrong with onboarding and no clear owner or next action.

IDS prevents this by forcing a discipline: before you discuss anything, you must be crystal clear on what you are actually solving.

Step 1: Identify — Get to the Real Issue

This is the hardest and most important step. Most "issues" that get raised are symptoms. The Identify step requires drilling down to the root cause.

EOS calls this process "The 5 Whys" — ask why something is happening until you reach the underlying cause rather than a surface symptom.

Example:

Raised issue: "Sales numbers are down."
That's a symptom. Ask why.
Why? "Reps aren't making enough calls."
That's still a symptom. Ask why.
Why? "They're spending too much time on admin work."
That's closer. Ask why.
Why? "We don't have a CRM workflow set up properly."
Now you have something actionable.

The real issue is not "sales numbers are down." The real issue is "we lack a functional CRM workflow." That's what you solve.

The Facilitator (usually the Integrator) has one job at this stage: help the team identify the root issue before allowing any discussion.

Signs you haven't identified the real issue yet:

The issue is framed as a symptom ("revenue is flat")
The issue is framed as a person ("John isn't performing")
The issue is too broad to solve in one meeting ("our culture is off")

Keep drilling until the issue is specific, solvable, and something the team has actual control over.

Step 2: Discuss — Say Everything That Needs to Be Said, Once

Once the real issue is identified, open the floor for discussion. The goal of Discuss is simple: get all relevant information and perspectives on the table.

The key constraint: say it once. IDS meetings should not be debates or therapy sessions. Everyone gets to contribute. No one should repeat themselves. No one should make speeches.

A good Discuss phase has these characteristics:

It is time-boxed (most issues should take 5-15 minutes total)
Every person who has relevant information gets to share it
The team avoids debating opinions — focus on facts and relevant context
Personal attacks or blame are out of scope

The Facilitator watches for two failure modes here:

Going in circles — The same points keep being repeated. This usually means the Identify step wasn't done correctly and the team is still debating what the actual issue is.

The rabbit hole — The discussion expands to include tangential issues. The Facilitator must bring the team back to the identified root cause.

A good rule of thumb: if you are more than 10 minutes into Discuss and you do not feel close to a solution, stop. Re-examine whether you correctly identified the real issue.

Step 3: Solve — Make a Decision and Assign Ownership

This is where most meetings fall apart. The Discuss phase ends, everyone has shared their view, and then... nothing concrete happens.

The Solve step requires two things:

A clear decision or next action — What will actually be done?
A single owner — Who is responsible for doing it?

Solve does not mean you have to fix the problem completely in this meeting. It means you decide on the next action that moves toward resolution.

Examples of bad "solutions":

"We should look into this more."
"Someone should reach out and get clarity."
"Let's revisit this next meeting."

Examples of good solutions:

"Sarah will audit the CRM workflow by Friday and bring a proposed fix to the next L10."
"We will not take on any new clients until our onboarding SOP is documented. Tom owns the SOP. Due: end of Q1."
"We are discontinuing Product X. Marcus will notify the three affected customers by end of week."

The solution must be specific, owned, and time-bound.

A Full IDS Walkthrough: Real Example

Setting: A 10-person SaaS company. Issue raised in L10 meeting: "The support team is overwhelmed."

Identify phase:

Is this the real issue? Ask why.
Why is support overwhelmed? "Too many tickets."
Why too many tickets? "Same questions keep coming in."
Why same questions? "Onboarding doesn't teach users how to use the core feature."
Real issue identified: Onboarding does not cover the top 5 support ticket topics.

Discuss phase (8 minutes):

Support lead: "We track ticket categories. The top 3 topics account for 60% of volume."
Product lead: "Those three topics were added in the last update. Onboarding hasn't been updated since Q3."
CEO: "We've talked about updating onboarding for two quarters."
Everyone has said what they need to say. Time to solve.

Solve phase:

Decision: Product lead will add a new onboarding module covering the top 3 ticket topics.
Owner: Product lead
Due date: Before next L10 meeting (7 days)
The issue is removed from the Issues List and becomes a to-do.

Seven days later, the to-do is complete. The issue is closed.

Tips for Running IDS Effectively

Prioritize issues before you IDS them. At the start of the Issues Solving portion of your L10, take 60 seconds to rank the issues list. Solve the most important ones first. You will rarely get through everything — start with what matters most.

Three items at a time. Do not try to tackle 12 issues in one meeting. Focus on the top three. Fully solve them rather than partially addressing six.

Separate personal issues from business issues. If someone raises "John isn't accountable," the real issue is almost always structural — unclear roles, missing scorecards, lack of feedback. Get to the root.

The Facilitator must protect the process. Someone has to be willing to interrupt discussion and redirect the team. This is the Integrator's job. Without a strong facilitator, IDS devolves into rambling.

Track all issues in one place. Keep a running Issues List that everyone can see and add to between meetings. Issues raised outside of meetings should go on the list, not get resolved through hallway conversations that leave half the team uninformed.

IDS and Your Issues List

IDS does not work without a well-maintained Issues List. The Issues List is where everything that is not on track, not going well, or potentially going wrong gets captured.

In EOS, every team member can add to the Issues List at any time. By the time you reach the Issues Solving Track in your L10, you already have a full list to prioritize from.

See our guide on running EOS scorecards to understand how scorecard metrics connect to issue generation — red metrics become issues, and IDS is how you solve them.

How TaskSpace Supports IDS

One of the most common EOS implementation failures is a disorganized Issues List. Issues get raised in Slack, in email, in side conversations — and by the time the L10 rolls around, nobody remembers what was supposed to be addressed.

TaskSpace keeps your Issues List structured and accessible. Team members can add issues between meetings, the list persists from week to week, and when you IDS an issue, the resulting to-do gets assigned and tracked inside the same system. Nothing falls through the cracks.

Stop solving the same problems twice. Try TaskSpace free at trytaskspace.com and run IDS the way it was designed — with a shared Issues List your whole team contributes to.