Loading…
28
Vent: The drawn-out process of finalizing our chart patterns
In my experience, when we revamped our team's data charts, I knew we had to make them clearer for people with vision differences. We used to depend only on slight shade variations, which didn't work well for everyone. I suggested adding patterns, like dots for one group and lines for another, to help tell them apart. Waiting for feedback from our testers who see things differently felt like it took forever. We had a tight deadline, but I insisted on multiple rounds of tweaks to get it right. Honestly, the extra time spent made the charts much easier for the whole team to use. Your mileage may vary, but in my view, being patient with these changes pays off. Now, I always include pattern options early in my design drafts.
3 comments
Log in to join the discussion
Log In3 Comments
samschmidt7mo ago
Yeah, when you said being patient with these changes pays off, I felt that. Been there with our analytics charts, and my big lesson is to bake in those pattern options from the start, like you do now. It cuts down on last-minute scrambles because your devs can code for them early. I always test with a color blindness sim tool too, it’s a game changer for spotting problems fast. Solid move sticking to your guns on the tweaks, it makes the end product way more usable for sure.
1
eric3597mo ago
Actually, rushing changes can often get products to market faster, which matters more than making everything perfect for all users. Baking in patterns early might mean you waste time on features no one uses. Color blindness sims don't always show real user problems, so field testing is key. Being too stubborn on tweaks can ignore feedback that makes the product better. I've seen projects fail because they got stuck in endless tweaks instead of launching.
2