New to this kind of software? You're in the right place. This post assumes nothing — not that you know what a "queue" is, not that you've heard of Jira or Monday.com, nothing. If a word needs explaining, it gets explained right where it shows up.
The problem this kind of software solves
Picture a small team. Someone emails a request. Someone else mentions a task in a chat message. A third thing gets scribbled on a sticky note. A week later, nobody remembers who's doing what, or whether the email ever got answered.
"Project management software" is just a website (or app) built to hold all of that in one place, instead of scattered across emails, chats, and sticky notes. Every request or task becomes one entry that everyone can see, with a status ("not started," "in progress," "done") attached to it.
The three words you'll see everywhere
- A queue is just a list. Not a fancy technical thing — think of it as one to-do list with a name, like "Requests" or "This Week's Work."
- A template is a starting kit. Instead of building your lists and settings from nothing, you pick a template and the software sets up a sensible starting point for you — already organized for a specific kind of work.
- An automation is a small "if this happens, do that" rule. For example: "if someone marks a request as approved, automatically move it into the working list." You set the rule up once, and the software does that step for you every time, forever, without anyone having to remember to do it.
That's genuinely most of the vocabulary. Everything else is a variation on those three ideas.
What actually happens when someone asks for something
Here's the part that's easy to get wrong if you've never used one of these tools: not everyone who asks for something should be able to add it straight to the team's active work.
A well-built system has a front door for outside requests — called a portal — that's just a simple web form. Anyone can fill it out, no account needed. What they submit doesn't land directly in the team's working list. It lands in a separate holding area first, where someone on the team looks at it, decides whether it's worth doing, and only then moves it into real work.
Think of it like a restaurant's host stand versus the kitchen. Guests talk to the host, not the chefs directly. The host decides the order things happen in. Nothing walks straight into the kitchen uninvited.
What you'd actually see, in one project
If you opened up a project built from a "Project Management" starting template, you'd find six separate lists (queues), each doing one job:
| What you'd see | What it's for, in plain terms |
|---|---|
| A request inbox | Where outside asks land first, before anyone decides they're worth doing |
| A list of big initiatives | The large, ongoing efforts everything smaller work belongs to |
| A backlog | Approved work that's waiting its turn |
| Active work | What the team is doing right now |
| Risks and important dates | Things that could go wrong, and deadlines that matter — kept separate so they don't get buried |
| Weekly summaries | A short recap written once a week, so anyone can catch up without reading everything |
Ten small automatic rules run in the background — the "if this happens, do that" kind described above. Two screens (called dashboards) show the big picture at a glance: what's overdue, what's in trouble, what's been done recently.
What this isn't (yet)
Honest note, because overpromising helps no one: this kind of tool doesn't automatically predict how fast your team works, and it doesn't have a fully automatic three-layer org chart of "big goal → medium goal → small task" — today it's a two-layer setup (a project → the individual pieces of work in it). If someone tells you a tool tracks "velocity" or "story points" automatically without real historical data behind it, be a little skeptical — that number has to come from somewhere real.
Ready for the deeper version?
Everything above describes the shape of the Project Management template that ships with OpenTechnologyApp. If you want the real technical detail — exact automation rules, every field, what the dashboards actually show — the full breakdown is here: Project Management: A Public Intake Portal That Feeds Triage, Not Delivery.
If this was your first time reading about project management software at all, you now know enough to understand that post — and enough to know whether this kind of tool would even help your team.