finance07Q: Roles instead of people
The problem I have with this flow is that I miss is the role instead of a person. Also when you for instance wants to have the reviews or input from certain roles or people need to be informed. Better said. The RASCI purpose like in the schematics of proper process flows.
When I have people in this, that can get outdated faster. Otherwise its more a project management tool instead of a workflow, action diagram.
So when will you put the RASCI in this tool?
What is your GDPR compliancy as you are filling in data of people instead of roles?
b_ragone
Dec 21, 2025A: Hey Finance07, thank you for your question. I'm having trouble understanding your questions.Generally, we have (a) 𝐭𝐡𝐞 𝐭𝐞𝐚𝐦 𝐜𝐚𝐧𝐯𝐚𝐬 where you can input your roles and (b) 𝐭𝐡𝐞 𝐩𝐞𝐨𝐩𝐥𝐞 𝐜𝐚𝐧𝐯𝐚𝐬 where you can input people. The reason why these are two separate canvases is because one person can sit in multiple roles.
So for a growing company you might want to architect your team design in a more forward-thinking way where 𝐨𝐧𝐞 𝐩𝐞𝐫𝐬𝐨𝐧 𝐬𝐢𝐭𝐬 𝐢𝐧 𝐦𝐮𝐥𝐭𝐢𝐩𝐥𝐞 𝐫𝐨𝐥𝐞𝐬 with the intention that eventually you would hire someone to take on one of those roles. This way, you won't have to reassign a bunch of steps. You just reassign the new person to the role. From there, that person would have all of the steps within the workflow canvas that they're associated with at varying levels of involvement (RACI)
Regarding GDPR compliance, we don’t currently provide formal GDPR compliance artifacts like a Data Processing Agreement (DPA) or Standard Contractual Clauses (SCCs). Puzzle is designed for process mapping, and data is stored in the United States. Until we complete our compliance program, we ask customers to avoid entering end‑user personal data and use Puzzle for non‑PII operational documentation. We’ll share updates on our privacy page as this evolves.