All Use Cases

Learn from your teammates

Somebody already solved this, and you will never hear about it

You can see what your colleagues have made with AI, and whose name is on it. Good ideas spread by being visible instead of by being announced.

Powered By

The Challenge

  • Somebody on your team already built the thing you are about to start building
  • You find out what a colleague made when they happen to mention it in a meeting
  • The person who is best at this is often the one least likely to bring it up
  • Good ideas travel by luck here: a demo somebody caught, a message somebody scrolled past
  • A new person cannot tell what normal looks like, because none of it is anywhere they can see

The Runwork Solution

  • The workspace home shows what your teammates have made, with their name on it
  • A saved skill carries its owner, so you know who to ask when you want to understand it
  • You see work while it is being made, not only once it is finished
  • A new person can look at what the team has already made and see how this company works
  • Each skill shows how often the team has used it, so you can tell what your colleagues actually rely on
  • Nobody has to announce anything for it to reach the rest of the team

What your team gets

The thing you were about to build

You start on a supplier comparison and see that somebody in finance made one in June. You go and look at theirs first.

A name to ask

A skill you want to understand has an owner. You ask the person who made it, which takes four minutes and no meeting.

The quiet one

The person doing the most interesting work is often the one who never mentions it. Their work shows up next to everyone else's.

A new hire reading the room

Somebody joins and looks at what the team has made. That tells them how this company actually works, faster than a document written a year ago.

What the team actually leans on

Each skill shows how many times it has been used across the workspace. That tells you which of your colleagues' work the team keeps coming back to, which is a better signal than how it looks.

What it does not show

It shows what people have made, not how much they have worked. There is no hours count and no activity score anywhere in it.

A Day in the Life

9:00 AM. You open the workspace. Before your own work, you see what the team made yesterday: a skill from somebody in support, an app from operations. You were not told about either.

9:40 AM. Somebody beat you to it. You were about to spend the morning on a supplier comparison. Finance made one in June. You go and look at theirs before writing a line of your own.

11:00 AM. A name rather than a search. You want to understand how a skill works. It has an owner, so you ask the person who made it instead of guessing from the outside.

2:00 PM. The quiet one. The person doing the most interesting work with AI has not mentioned it once. It is sitting in the workspace with their name on it, which is the only reason you know.

4:00 PM. A new starter reads the room. Somebody joined on Monday. They have spent an hour looking at what the team has made, and they now know more about how this company works than any onboarding document would have told them.

5:30 PM. Nobody announced anything today. No demo, no all-hands, no message asking people to share what they are working on. The work was simply where the team already was.

Frequently Asked Questions

What does the activity feed actually show?
What people have made and changed in the workspace, with the name of the person who made it: skills, apps, and the things the team has built and deployed. It is a record of work rather than of effort, which is why it reads as a place to find things rather than as a report on anybody.
Does it show how much people are working?
No, and that is the important half. There is no hours count, no activity score and no measure of how busy anybody is. It shows what somebody made, so the only thing a person can be seen for here is having built something. That is a deliberate difference from a productivity view, not an omission.
Can everyone see this, or only admins?
Everyone. It renders on the workspace home for every member, which is what makes it useful: the point is that a colleague finds your work without a manager in the middle passing it on. If it were admin-only it would be a management report, and it would do none of the things this page describes.
How is this different from the team dashboard?
Different reader, different question. The team dashboard is for whoever is responsible for AI going well across the team, and it answers who needs help. This is for you, next to your own work, and it answers what your colleagues have figured out. One looks after people; the other is how you avoid rebuilding something that already exists.
What do I do with something I find?
Usually nothing, and that is the point. A skill your colleague saved is already reaching your AI through the workspace, so finding it is not the step before using it. What changes when you see it is that you know it exists, you can see what the team uses it for, and you know who to ask about it.
Is this the same as the skills my AI already gets?
No, and the difference is which direction the work travels. Saved skills arrive in your AI whether you asked for them or not, so you get them without knowing they exist. This is the other direction: you go and look at what the team has, on purpose, because you want to know what is going on.

Related Use Cases

Start keeping what your team figures out.

Start a 14-day free trial. No credit card required.