Repository navigation
A (relatively) simple way to track projects across boards #3200
Unanswered
mile357
asked this question in
Ideas and Issue Triage
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi Everyone,
I feel like a heretic coming in here to talk about initiatives, cross-board projects and (gasp) Gannt charts, but as we started using Fizzy we really liked the simplicity of the tool and how quick and easy it is to get going, but there was still a level of coordination missing.
We're not a software development shop, we run an IT department that provides services for various portfolio companies in different industries. It's a very different environment than the typical fizzy user, and we had a few needs:
We wanted to do all that while maintaining the feel of fizzy, changing the UI as little as possible, and keeping things as consistent as we possibly could.
The implementation we wound up going with is using tags for initiatives, and making an initiative tracking page for people to look review occasionally. It looks like this:
Basically, you add tags to cards like normal, and some tags might be associated with a project. In the "initiatives" page you can then find a tag, click on it, give it a start and end date (and a color) and it gets added to a gannt chart. That's really the basic idea, just extending tags a little so that some can be used to track initiatives.
We also mimicked the "step" idea, so a card has steps, and initiatives have "Milestones" -- the big things that need to get done for a project to be complete. These are tracked manually -- ideally in your weekly or biweekly planning or whatever you'd look around and go "Do we feel like this milestone is done?" and then check the box if so. Progress is reported not on cards complete, but on milestones, so it'll be less granular, but probably more accurate.
Leaders can look at initiatives when planning, and everyone else really only has to engage if they want to. The one way we decided to transmit feedback from the initiatives back to the boards is that, if an initiative is overdue, cards associated with it get a red border.
Again, a lot of this is antithetical to how 37 signals works, but I think other organizations might appreciate the ability to simply track initiatives and have less obtrusive deadlines, not on a task basis, but on a major project basis.
There are a few other nice-to-have features that I won't go into here, but feel free to ask me any clarifications. You can find the code here:
https://github.com/mile357/my-fizzy
ONE IMPORTANT FINAL NOTE: I vibe coded most of this, so I feel like the ideas and implementation are decent, and so far it has performed OK (we're still working out bugs so the repo will get updated), but you may want to have a real professional check it out before using it.
I imagine most people will ignore this, but if you've felt that some cross-platform project management and/or initiative coordination would be useful go nuts.
Thanks!
All reactions