Related Posts
Who’s ready for IOS 14.4!?
Additional Posts in Designers
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
Who’s ready for IOS 14.4!?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Download the Fishbowl app to unlock all discussions on Fishbowl.
Copy and paste embed code on your site
Send download link to your phone
OR
Scan your QR code to download
Fishbowl app on your mobile
Mentor
For the most part that isn't a personal decision. The org you work for should have a set process.
Func specs are only done if your company is waterfall and not agile, or if the tech team is offshore.
In the agile world, there are many agile ceremonies to avoid such a document. And most documentations are done via user stories.
For me, it depends on the complexity of the project. I don't often write functional specs unless I'm introducing something new to the design system. However, I do share prototypes often because I create a lot of data visualizations and there are a lot of interactions and states to consider. I'll also include notes in my Figma if there are certain things I want the dev team to be aware of.