Hi All,

Welcome to the May episode of “What’s Good?” 

This month I have the pleasure of hosting a guest blog from Robert Janezic on design. Many of you may be aware of Robert’s Tableau UI Kit that helps developers with prototyping. What truly impresses me is Roberts both depth and breadth of technical skills. I hope readers today get to take away Robert’s sentiment around embracing being better designers.

Before this you will have seen some of his own Tableau Public content, such as the Beatles viz, Liv and Ebb & Flow. All wonderful in design.

CJ: Robert, Thanks for joining. Let’s start by diving into your own journey. Can you share with us a little more about the transition to become a designer? At what point do you feel you become a designer… instead of say, an analyst?

R: Happy to be here CJ, appreciate you reaching out. My transition to becoming a designer wasn’t straightforward and really came from a necessity in our team (Tableau COE at JPMorgan Chase). We started creating applications for our users and the need for a designer became more apparent. We needed to create the designs before the engineers coded everything. I already had a good eye for design from my years of creating Tableau Public work, so it just made sense that I would be the person to create these designs. I already wanted to get into UI work before that, so I really took it upon myself to learn all I could about it.

It was at this point I felt like I became a designer. I say that because all my work was focused on design, and I was in Figma 90% of my day. To be honest I thought the transition would be easy, because in my head I was saying “I can create well designed Tableau dashboards so the two should overlap, right?”. Ya I was just dead wrong lol. It became very apparent that there wasn’t that much design skills overlap between a Tableau dashboard and an entire application. 

I now must think about:

• States (Hover, Active, Focus, Disabled)

• Smaller components (Dropdowns, Switches, Radio buttons, Text Fields, etc.)

• More text options (Line height, Paragraph spacing, Kerning, etc.)

• Design Systems (Type Scales, Color Palettes, Spacing Scales, Componentization etc.)

• Engineer handover (Making sure the engineers have what they need to copy 1-1)

• And a lot more

In general, you can get away with not thinking about any of the above while designing a Tableau dashboard. So, it was overwhelming at first but like everything with time and practice I got the hang of it. I can confidently say this is what I want to do for my career, I absolutely love it!

CJ: What I’m really impressed by with your UI Kit is not only its functionality but how it reflects on your business acumen of seeing something that can be done better and building something to fill that gap. Can you share a little more around this journey, was it ignited by product or business thinking?

R: I got the idea for the Tableau UI Kit about a year and a half ago. The Figma community has a TON of UI Kits, but most of them are for applications and websites. When I first started there was nothing related to Tableau and thought “wow, if someone wants to prototype their dashboard, they have to do it manually by hand and it most likely won’t look like Tableau and will take a long time”. I know that to be true because I used to do the same thing, and both of those statements applied. Not only that, but I used to do my dashboard prototyping in PowerPoint and it was an absolute nightmare.

The entire Tableau UI Kit took me about six months to build and was easily the most work I’ve ever put into a side project. Here’s the steps:

  1. Procrastinate

    1. Starting is always the hardest part for me. But once I do, I’m all in!

  2. UI Kit and Design System research

    1. This was a really important step because it saved me a lot of potential rework. I ended up still having to do some rework, but this minimized it substantially. Plus when I do something I want to make sure I’m doing it right and not doing it half-heartedly.

  3. Development

    1. This was the most technical step and really pushed my Figma skills to its limits. I was deep into advanced features/tricks every single day for months (I think in autolayout now). There were points where I got bummed out because I had so much work left to do and there were some days I couldn’t figure something out. But taking it day by day and frequently stepping away from the computer is the best way to tackle larger projects (I usually only work on side projects for 2-3 hours at a time).

  4. User Feedback

    1. As with everything you create, getting feedback is very important. Although I found it difficult to get feedback because the Tableau UI Kit is such a new concept for most of the community. I had to trust my instincts on a lot of things. Some of those instincts turned out great, others not so much. But you just adjust and keep it moving.

  5. Create website and gumroad store

    1. As some of you may know I’m a huge fan of Webflow and love jumping at the chance to create a new website. At first I didn’t know if I was going to create one, but having an official website adds legitimacy (and you need that especially if you’re charging for it).

    2. The Gumroad stuff was brand new for me and I did pretty extensive research on what service I wanted to use (It was between Gumroad and Lemonsqueezy). I chose gumroad because of the simple fee structure and the great reputation it’s had. Hosting a product on Gumroad taught me a lot about marketing and the important role it plays.

  6. Marketing

    1. If you’re creating something DO NOT SKIP MARKETING (I almost fell into this trap). After I finished development I got the urge to just release it. But I had to tell myself not to do that, because it would have been a disservice to the value the product brought. People really need to understand what it is you’re creating and why they should care. 

  7. Release

    1. Release the dang thing already!!

  8. More Marketing

    1. Just because you released doesn’t mean it’s done and over with. Most people probably missed your social media posts. Even if they did see them, they’re still probably not convinced of the value it may offer them. So you have to keep updating people on new versions, talks you’re giving and reminders that the product still exists.

  9. Even More Marketing

    1. Forreal, just do more marketing.

I’ve got to admit I spent a long time deciding if I should make it a paid product or not. Because let’s face it, most of the resources in the community are free and I got the feeling that people would look down on me for making it paid. So, I asked around to some people I trust. They told me “you 100% should make this a paid product, it fits an area of the market that has not been tapped into yet”. 

I took their advice and am happy I did so. For anyone who’s reading this – if you have an idea that adds value for others, don’t be afraid to stick your neck out and turn it into something more than an idea. I’ve really gotten the entrepreneurial itch, and I don’t see it going away anytime soon.

CJ: Could you share with us some of your own personal processes with design in respect to site mapping, wireframing and prototyping? What does the E2E Journey look like to you?

R: This is a great question, and one that needs to be discussed more. Let me walk through the design process I take on most of my projects (this applies to Tableau work as well):

1. User research (understanding user behaviors, needs, and motivations)

2. Define the problem (what user problem will you be trying to solve)

3. Ideate (brainstorm on a range of creative ideas and solutions that address the problem)

4. Sitemap (hierarchical diagram of the application)

5. Wireframe (low-fidelity, basic layout and structural guidelines)

6. Prototype (mid-to-high-fidelity, design model of the final UI)

7. Feedback

8. Iterate

9. More Feedback

10. More iteration (if necessary)

11. Handover to developers

Skipping steps is the fastest way to low adoption and rework.

CJ: If you’d like to take a further look you can view the site here, or find it on Gumroad for purchase here.

CJ: Your personal website is a thing of beauty. What have been some of your learnings from doing web design?

R: Appreciate that! I’ve learned that well designed applications/websites add legitimacy and users can feel when they’re not designed well. They may not have the vocabulary to explain it, but they know it when they see it.

Don’t just take my word for it, look up “Design web statistics” and you’ll see exactly what I’m talking about. The idea that these same statistics wouldn’t apply to Tableau dashboards doesn’t make sense to me.

CJ: What are some common design pitfalls?

R: I talked about one of the biggest pitfalls earlier, which is not following processes. The worst thing you can do is just go for it. I’ve seen time and time again people just going for it and having to do a lot of reworks. By following specific processes, you get a better result, but also significantly cut down on the potential for rework.

Another pitfall I see is people focusing on features over usability. This thinking often hurts startups and significantly reduces the number of sales conversions. I would suggest focusing on doing a few things really well and having a great user experience rather than adding every feature under the sun. Having a bad user experience is one of the quickest ways for a user to never want to use your tool again.

CJ: How do you see Tableau in the broader community? What tips would you give individuals that are immersed in the Tableau community to learn more about design?

R: I think which community you go to is really important. Do not feel like all your information should come from one community!! If I have a tableau question or want to learn more, I’ll go to the Tableau community. If I have a Figma question or want to learn more, I’ll go to the Figma community. This applies to all communities; you go to the experts to learn more.

If we’re talking about Tableau and design, I think people have the most to learn from User Interface designers. I say that because User Interface designers work in a structured environment, not unstructured (in general). Almost all Tableau design (especially in day-to-day business work) is structured. You’ll also get the added benefit of understanding how to design an application or a website. It’s really a win-win all around.

CJ: With this in mind – who are some of your favorite designers to follow? Do you have any resources that are a good starting place to learn better design?

R: Here’s some great designers you can follow on twitter: @jamesm, @DannPetty, @Ridderingand, @charliprangley, @alyssaxuu, @jsngr, @joeyabanks, @steveschoger

That’s a pretty good list to get started. Obviously there’s a lot more, but you can just get to the people I’m following on Twitter for more.

CJ: I fondly remember dialing into a Twitter Spaces call where you were discussing some quick tips for those just getting started. Can you give us 5 of your top tips for using Figma?

R: Ohhh I’ve got a lot of these haha. Here’s my top 5:

1. Use more frames.

2. Stop using Groups. Generally the only reason to use Groups is for file organization.

3. Use Autolayout way more. Once you understand the power of autolayout you’ll wonder how you ever did anything before it.

4. Learn important keyboard shortcuts. You’ll be able to work a lot faster.

5. Use Figma for almost everything. At this point I use it for prototyping, presentations, icon design, graphic design and essentially everything when it comes to design. My point is you can use it for a lot more tasks than you may think.

CJ: Thank you so much for joining today. Is there anything you’d like to share about the remainder of the year, particularly in regards to your journey with Figma and your Tableau UI kit?

R: I’m currently working on v1.5 for the Tableau UI Kit and I’m excited for the new features coming. I’ve collected a lot of feedback from customers and I’m taking all of it into consideration for future releases.

Outside of the Tableau UI Kit I’ve been thinking about and workshopping new tools for Tableau users. I’m pretty in tune with the issues users currently have with Tableau, and I’m trying to fill that gap with tools that immediately add value at scale.

Thank you for having me CJ, really enjoy the What’s Good series!

CJ Round-up:

I revisit Roberts Tableau Public page often for inspiration. It is a goldmine when combining good design with technical chart types. I can’t speak for the rest of the community but I would love to see a return to the public vizzing again. I always enjoy profiles like Robert’s where I think “wow, how was that made?”

Roberts move towards becoming a designer full time is really inspiring and I hope the tips shared in this blog can help others with making that step towards better design. Do take the opportunity to reach out to Robert with any further questions you may have.

Having had the pleasure of looking at the UI kit during its test phase and more recently through acquiring a license through the company I have to say I am super excited for the future release of v1.5. I wish to congratulate Robert on reaching a milestone in sales recently, paying testament to his hard work and his desire to help others become better designers.

See some of you in Vegas in a few weeks.