How to manage projects in a small business
On a Monday in December, Priya Nair at Calder Group asks Leo Tan whether the Booking Tool still goes live on January 18, because staff training is booked around it. Leo, the founder of Fieldline Software, doesn't know. By lunch he has the answer from three conversations. Nina Shah is waiting on a room list that changed when an engineer's comment moved a wall. A release for the Corran Theatre's ticketing app has waited four days on one code review. Nobody has asked Calder's IT team for a test sign-in, because everyone assumed someone else had.
Fieldline has 14 people, three projects on top of the business itself, and nobody whose job is project manager. Work gets agreed in a chat thread and never becomes a task with a name and a date. "Can you take the theatre's seat map?" gets a nod, and a nod isn't a yes. A stuck task makes no noise until its date passes, so the founder hears about a slip when a client asks.
The fix is a small structure and a short weekly habit, shown here in Arkscape, a project collaboration and task management tool.
One board and one lead per project
Give every project its own board, and only projects get one. Calder's Booking Tool, the Corran Theatre ticketing app, and Fieldline's own move to a new cloud host each have a start and an end. Payroll and support don't end, so they don't get one. A board per department mixes three projects into one list.
On each board, use the columns as the project's phases in order. For the Booking Tool: Design, Build, Security review, Launch. Each task is a card with a due date and a title that says what done means. "Desk map import tested with floor 2 data, Fri 11th" is a task. "Map" is a topic.
Then name one lead per project, and not always yourself. Nina leads the Booking Tool, Ana Weiss leads the theatre app, and Tom Hale leads the cloud move. The lead keeps the board true, and Leo's job becomes the review.
In Arkscape, each project is a group, with an Arkboard, Discussions, Files, Members, and Reports tab. Choose an internal group when only your company works on the project, like the cloud move. Choose an external group when someone outside will join, like the Booking Tool. The type can't be changed later, so pick external if anyone outside might join. Give each project's lead the group's Lead role, and set the project's end date from the Target completion card on the Reports tab.
One owner per task, who has said yes
Every task gets one name. "Nina and Ana" means each thinks the other has it. Two people can share the work, but one owns it.
Ask for the task, and wait for an answer. Ownership starts when the person agrees, not when their name is typed in. A no on Monday ("I'm on the theatre release until Wednesday") costs a short conversation. A silent miss on Friday costs the date. Until the yes comes, the task is still the lead's.
This includes people outside the company: clients, partners, and freelancers. If someone owes you something a date depends on, put them on the project with their own task and ask for the same yes. Jo Park, a freelance designer, draws the icons the desk map shows, so Jo belongs on the Booking Tool board. The theatre's box office manager only needs to approve the seat map, so she gets one task.
In Arkscape, open a card and choose Assign to... under Responsible. Until the person accepts, the card shows Invited, not yet accepted. They answer from Ark Requests with Accept or Decline, and a decline can carry a short message, which comes back on the Updates tab. Once accepted, the same card appears on their own board, Your Ark. To bring Jo in, open the group's Members tab, choose Invite, then Invite others via email. For the box office manager, open a card on Your Ark and choose Add people from its ... menu; a card holds up to 10 people. People you invite join with a free account.
Fifteen minutes a week on what's quiet
Once a week, read each board for four things, in this order:
- What is overdue. Give it a new date you can keep or cut it, and tell whoever is waiting on it today.
- What hasn't been accepted. Ask the person for their yes or their no.
- What has no owner. Give it one, or decide nobody needs to do it.
- What has gone quiet. A task nobody has touched for two weeks is usually stuck, not slow. Ask what it's waiting on.
The last three catch a slip before it's late. At Fieldline, a review two weeks earlier would have shown "Ask Calder IT for a test sign-in" untouched for 16 days and "Review the theatre release" with no owner. Leo reads the list before the Monday stand-up and asks only about that.
In Arkscape, open the project group's Reports tab. The tiles at the top count Overdue, Due in 7 days, No one responsible, Not accepted yet, and Quiet for 14 days; select a count to open the cards behind it. Quiet counts open, undated cards nobody has touched for 14 days, so date anything that matters and it will show as overdue if it slips. Group reports follow the plan of the group's owner. Every Business plan includes them, and by default the group's admins and leads can open them.
A weekly routine in Arkscape
- Monday, before the stand-up: for each project group, open Reports and read the five tiles.
- For each overdue card, move its due date or complete it, and tell the people affected the same day.
- Assign every card under No one responsible, and message each person under Not accepted yet.
- Give each card under Quiet for 14 days a date and an owner, or complete it.
- On each board, open Activity from the ... menu and choose 7 days to see any due date that was pushed back.
- Friday: on Reports, choose 7 days, and use Copy as text under Completed for the week's status update.
Each person's own list across all three projects is covered in how to manage multiple projects at once.
Where this method stops
This method tells you who is doing what by when. It doesn't run the rest of the business. Arkscape has no timesheets, fee tracking, or invoicing; accounting software and a time-tracking tool cover those. It isn't a CRM, so your sales pipeline stays in one. If moving one task's date should move ten others, you need scheduling software with dependencies; Arkscape has a board and a calendar, not a Gantt chart.
No review fixes a company running more projects than it has people for. If the same names are overdue on every board, pausing a project or moving its date is the founder's call.
Arkscape's Business plans are priced per user per month, the owner included: Growth is $25 and Scale is $40, and both start with a 14-day trial. For Fieldline's 14 people on Growth, that's $350 a month. Outside people in its groups, like Priya and Jo, aren't Fieldline's users, so they add nothing.
Common questions
What is the best way to manage projects in a small business? One board and one lead per project, one owner per task who has agreed to it, and a 15-minute weekly review of what's overdue, without an owner, not yet accepted, or quiet.
Does a small business need a project manager? At 10 to 20 people, usually not as a full-time role. Each project needs a lead who keeps its board true, and the founder needs 15 minutes a week to read across all of them.
Should freelancers and clients see the project board? Yes, when they owe something a date depends on. Put them on the project with their own task. For a single question or approval, share that one task instead.
Can I manage small business projects in a spreadsheet? Yes, for one or two projects with one person keeping it current. Use columns for owner, accepted, due date, and last updated, and filter for the four checks. It stops working when each person also keeps a private list.
Read next: how group reports work, internal and external groups, and how to delegate tasks to team members.