Related Posts
Favorite national park to visit in July/August?
Potential opp on the short side for TSLA?
- X
Additional Posts in UX and UI designers 🚀
6 articles you must read if you are starting as a UI/UX Designer
📍How to become a self‑taught UI/UX designer
https://lnkd.in/dUgxXwjP
📍The ultimate Figma resource archive (2021)
https://lnkd.in/dQUgAdJc
📍A step-by-step guide to your first UX case study
https://lnkd.in/d5BB2wPW
📍All you need to know about colours in UI Design — theory & practice
https://lnkd.in/dTC-5mGy
📍The UX Designer’s Guide to Typography
https://lnkd.in/dmUxKhtc
📍Design / UX: Getting That First Job
https://lnkd.in/dJhnVPMQ
👇Let me know in the comments if you found this helpful :)
New to Fishbowl?
unlock all discussions on Fishbowl.



Frankly, I find that a design for something 6-12 months out is usually such an uncertainty with Agile development that you don't want to go beyond wire-frames and medium-fidelity prototypes. Requirements and priorities change, as does everyone's understanding of those requirements and priorities, and so investing significant time on those speculative designs is usually wasted. Odds are you are going to throw away most of it when you actually put together the final designs.
For tactical work, create detailed, complete, designs.
For strategic work, don't go beyond concept sketches and low to medium fidelity prototypes. You want it to be complete enough that people can discuss it, plan for it, get excited about it, etc. But, communicate that it is conceptual only and everything could change.
We have teams that focus solely on design systems, while others focus on immediate needs. It’s not perfect, but it allows for a steady build of the design system without pulling people away to work on something else.
Unfortunately, we're all-in-one. I can't change the team structure. I was hoping that people would have some suggestions on how to handle design file management and status indicators within the files (decision tracking tools would be helpful too), since leadership wants the workflow patterns documented, but realistically a workflow might be substantially larger than design system components. I probably shouldn't have said design system in my original post. There is a company wide design system and there is a component library for the app, but they want us to doc workflows within the component library as references via Figma embeds. I just feel like keeping those files up-to-date is going to be a challenge.
Yeah you need a design system team along with your day to day design team - if you start with an existing system it should not take years to create the baseline
We already have that. We have a company design system and our app has its own set component library in Storybook. The problem is we - the designers in the scrum teams - have to manage entire UX workflows for our product that are at different stages of done (that's the part leadership wants to see documented) and I am looking for how best to communicate that within the design files because realistically a workflow might involve 16 features that are not going to be prioritized consecutively in an agile dev team. It's absolutely a mismatch of how the agile methodology is supposed to work, but I can't change the people. I can only change design files.
I work on a nonprofit public-facing site with a 2-person team. We typically do two sets of mockups: 1) one flow showing the overall experience for the feature or area of the site, both the as-is and proposed future state, which we use for business review and technical/architectural conversations; and 2) separate smaller flows for each single feature or section that will be worked in 1-2 sprints, narrowing to just that iteration and scope, so the dev team has a clear picture what to build.