What tool stack does everyone use for project management? Especially those who have multiple proj...

What tool stack does everyone use for project management? Especially those who have multiple proj...What tool stack does everyone use for project management? Especially those who have multiple proj...

The network for creativity

Join 1.25M professional creatives like you

Connect with clients, get discovered, and run your business 100% commission-free

Creatives on Contra have earned over $150M and we are just getting started

Back to feedPost

Bobby Jocson

max

• Jan 15

What tool stack does everyone use for project management? Especially those who have multiple projects going on simultaneously. Right now we have a combination of Trello, Slack, and Frame. We are at the point we need something a bit more robust, but I don't want to go overkill. ClickUp has a lot of things I like, but sometimes feels overkill.

Hugo Jackson

pro

• Jan 17

Slack, Figma and Asana at work, although i hate it!

Bobby Jocson

max

• Jan 18

What would you want if you could create it?

Hugo Jackson

pro

• Jan 19

I think Asana has all the right things but just in a way that is overly complicated for no reason. So something really stripped back I think

Ronak Jain

• Jan 18

Notion Kanban and Slack.

Katie Borg

pro

• Jan 19

We use ClickUp at work, which I've actually liked a lot. I feel like you can ignore the features you don't need and work within a more limited toolset if you want.

Agustin Dell Aquila

max

• 13h

framer tip for noobie clients: build with component variants in mind

Most designers build a hero, then a features section, then a pricing block. When the client asks to change the button color, they update it 23 times.

When you build with variants: → One component change updates the entire site → The client can swap layouts without breaking anything → You hand off a system, not a static file

↓ What's the one thing that changed how fast you work? Genuinely curious.

Stephanie Asoegwu

pro

• 8h

Building with variants from the start is such a game changer — it's one of those habits that feels like extra work at first but saves SO much time with clients. Component thinking > static designs!

Filip Vuković

• 16h

Most teams build a UI kit. Then the product grows, new features get added, new designers join, and every screen starts looking slightly different. Not broken, just inconsistent. Death by a thousand exceptions.

When I joined a B2B product environment, there was a basic UI kit, but no tokens, naming convention, or rules for how components should behave across contexts. Design debt was building quietly.

I didn’t start by redesigning screens. I started by defining the foundation: color tokens, spacing scale, typography, component states, and naming conventions. Only after that did screens get revisited.

The result: faster feature design, one reference point for developers, and less inconsistency compounding over time. The system is now used in production across multiple products by 1,000+ daily users.