# How do teams set up monday.com workflows without getting lost in the customisation options?

<p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">I'm pulling together some notes on how teams set up <a class="a a--md" elv="true" href="https://www.g2.com/products/monday-com/reviews">monday.com</a> workflows without getting lost in the customisation options. The approach that comes through on G2 is to map the process first, the stages, owners and statuses, then build boards around that map from the start, adding columns only when the team actually needs them. Getting lost tends to happen when building starts before the process is clear, which leaves columns nobody uses, and managing agents across several workspaces without one central view is a newer version of the same question. The flip side is the reason teams choose it: boards and workflows can be shaped to fit almost any process, so once the map exists, the board fits the team rather than the team fitting the tool.</p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">There seem to be two kinds of team in <a class="a a--md" elv="true" href="https://www.g2.com/categories/project-management">project management</a>, and they experience the same flexibility differently. A team that already knows its process gets a working board quickly, since the interface is described as intuitive once the structure is clear. A team still working out its process can keep adding columns indefinitely, because nothing in the product signals when there's enough. monday.com suits the first kind best, and the second kind gets there by deciding the process before the board.</p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">On the build:</p><ul>
<li>Did you start from a template or from an empty board?</li>
<li>Which columns did you add only after a few weeks of use?</li>
</ul><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">On keeping it tidy:</p><ul>
<li>Have you ever stripped a board back to fewer columns?</li>
<li>Who decides when a new workspace or agent gets added?</li>
</ul><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">What would you set up differently if you were starting your first board today?</p>

##### Post Metadata
- Posted at: 1 day ago
- Author title: Marketing Executive
- Net upvotes: 1


## Comments
### Comment 1

&lt;p&gt;&lt;span style=&quot;color: rgb(0, 0, 0);&quot;&gt;Mapping the process first and only adding columns when we actually needed them kept our boards clean. The flexibility is great once the structure is clear.&lt;/span&gt;&lt;/p&gt;

##### Comment Metadata
- Posted at: about 4 hours ago





## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4