From Sticky Notes to Sprints: A Step-by-Step Guide to Running Projects with Flitz Work
Still tracking tasks across WhatsApp, spreadsheets and sticky notes? Here's a practical, step-by-step guide to setting up a Jira-style Kanban board and roadmap inside Flitz — no extra subscription needed.
If your team currently tracks work in a shared spreadsheet, a chat thread, or a wall of sticky notes, you already know the pain points: nobody knows what's actually in progress, deadlines slip silently, and customers keep asking "what's the status?" by email. Many Swiss SMEs put off adopting a proper ticket tracker because tools like Jira feel built for software teams, come with yet another monthly invoice, and sit completely disconnected from the rest of the business.
Flitz Work solves this by putting a Jira-style Kanban board and roadmap directly inside the same platform where you already do invoicing, accounting, CRM and HR. No separate login, no separate subscription, no data silo. Here's how to move from manual chaos to a structured, visual workflow in a handful of steps.
Step 1: Set up your first board and customize the columns
Start by creating a project. Flitz Work gives you a default Kanban board, but the real value is that columns are fully customizable per project. A marketing team might want "Idea → In Review → Scheduled → Published", while an operations team might prefer "Backlog → In Progress → Blocked → Done". You can add, remove, rename, and reorder columns at any time as the project matures — there's no rigid template to fight against.
What to expect: within minutes you'll have a board that actually matches how your team talks about work, instead of forcing your process into someone else's software.
Step 2: Replace your task list with tickets
Take whatever is currently scattered across spreadsheets, emails, or sticky notes and turn each item into a ticket. Assign a type — Bug, Feature, Change, or Support — each with its own icon and colour, so anyone scanning the board instantly understands what kind of work it is. Add a profile-picture assignee so ownership is never ambiguous.
What to expect: your first board will look messy for about a day. That's normal — it means you're finally surfacing all the work that was previously invisible.
Step 3: Drag, reorder, and keep the board moving
This is where Flitz Work feels like Jira: drag tickets vertically to reprioritize within a column, or horizontally across columns as status changes. There's no "updating a spreadsheet row" step — the board itself is the live source of truth. Team members get @mention notifications when they're tagged in a comment, and cycle-time tracking runs quietly in the background so you can later see how long tickets actually take from start to finish.
Step 4: Group related work into Epics
Once you have more than a handful of tickets, group related ones into an Epic — for example "Website Relaunch" or "Q3 Client Onboarding". Give each Epic a custom colour and a start/end date. This gives managers and fiduciaries a bird's-eye view without having to open every single ticket.
What to expect: Epics turn a pile of tickets into a readable story — useful for status updates to partners or clients who don't need ticket-level detail.
Step 5: Build the roadmap timeline
Switch to the roadmap view to plan delivery over time. Each Epic or ticket appears as a bar on a timeline — drag the bar to reschedule it, or drag its edges to resize the duration. Use the Q1/Q2/Year filters to zoom in on the current quarter or step back for an annual view. This replaces the manual Gantt chart or planning slide that usually gets outdated the moment you finish building it.
What to expect: a living roadmap that reflects reality, because updating it takes a drag-and-drop instead of a rebuild.
Step 6: Bring customers and your chat into the loop
Instead of forwarding status updates by email, invite customers to collaborate directly on the board via the Customer Portal. They see progress in real time and can comment where relevant, cutting down the "any update?" messages. Internally, turn on the chat mirror so comments and status changes post automatically into your linked chat channel — your team stays informed without needing to open the board constantly.
Step 7: Connect roles, watchers, and code
As the project grows, assign per-project roles so the right people have edit access while others can only watch. Add watchers to tickets that matter to stakeholders who aren't directly assigned. For technical teams, the GitHub-branch integration links tickets straight to the branch where the work is happening, so developers and project managers stay in sync without manually cross-referencing ticket numbers.
Why this matters for Swiss SMEs
Small and mid-sized businesses rarely have the budget — or the appetite — to run a dedicated project management tool alongside their accounting and CRM software. Flitz Work removes that trade-off: you get the drag-and-drop Kanban experience teams expect, with Epics, roadmaps, customer collaboration and chat integration, all inside the platform you already use for invoicing and MWST-compliant accounting. No new vendor, no new invoice, no new login.
Ready to move your team off sticky notes? Explore Flitz Work and set up your first board today.