Tag Archives: ITIL

Building a culture of trust

Posted on by
Reply

We talk a great deal about results, delivery and giving our best in the workplace. But what makes that possible? What are the most important factors in achieving results? Well there are several, obviously, but one of the most important in that of trust. Without trust, we don’t get results.

So I got thinking – and when I get thinking I get researching. And when I get researching I get writing!

Seems to me there are 2 key aspects of trust –being able to trust people yourself and also being trusted by others. Obviously we’d love to have both of them nailed. And some people just inherently seem to be trustworthy. But what are they doing that allows them to be trusted?

Three Elements of Trust

In a recent article [HBR], Jack Zenger & Joseph Folkman outlined their “Three elements of trust”. I’ll describe them here .

  • Positive relationships

Seems obvious but we have more trust in people we have enjoyable interactions with. That might be someone who acts as a catalyst for getting things done, someone that is great at resolving conflicts or someone that provides great feedback. Or perhaps it’s someone who’s empathetic nature makes us feel comfortable. Whatever the reason, they make us feel positive, and that leads us to trust them.

  • Good judgement and expertise

It’s much easier to trust someone who comes with a proven track record of expertise and achievements. If you can clearly demonstrate that you know your subject area and how to do your job well then it’s easier for others to trust you. At highly-skilled organisations the base level of job excellence is kinda assumed, but make sure you add value to the calls you’re invited to and that your opinions and ideas make a tangible difference to others. Speed can also be important here. Trustworthy people often act fast to resolve issues, and many times anticipate problems before they happen.

  • Consistency

These are people that you can rely on. You know they’ll go the extra mile if they can, and that they back up their words with action. One of the best pieces of advice I ever received was that of “Deliver, Deliver, Deliver”, i.e. carve out a reputation as someone that always delivers and you’ll become an indispensable go-to person for others. True consistency is hard to achieve, we all make mistakes, but if you can build that reliability factor then people will trust in your capabilities. Giving yourself that chance to succeed is key here. Set expectations; keep your commitments and Deliver, Deliver, Deliver. [QA]

While these make a lot of sense, there’s a bit more to it IMHO. So I have some of my own.

  • Don’t be a jerk

We all have a bit of jerk in us. We know when we’ve been unfair to someone. The key is to detect the behaviour coming and squash it at source. Developing emotional intelligence and self-awareness is the key here. Don’t take your bad day out on someone else. If you’re a jerk, then people will give you a wide berth.

  • Equanimity

Rather like the best poker players, you’ll find that key leaders respond in the same way when things are going badly and when they’re going well. You don’t see overreactions or huge displays of emotion. This can come across a little robotic, but really helps when the s hits the f. If you know someone is going to respond to problems with a cool head then they rapidly build your trust.

So those are some factors that you can employ to be seen as trustworthy. But how can you develop your own team or colleagues to be people you can trust? How can you help them?

How to build a trustworthy team culture

  • Autonomy

You have to let people get on with their tasks and resist any urge to micromanage. Give your team the freedom for them to say “hey I got this”, for them to let you detach from the nuts and bolts and trust in their delivery. Just like if you’ve ever tried to do something for a 3 year old child that they can do themselves – they’ll soon tell you “I’ll do it myself!” Maybe an adult won’t be so honest so it’s up to us to provide our teams with the autonomy to be able to take action and deliver [WNEXT]. Obviously then they need to deliver of course! J

  • Freedom to fail

I have no problem with my team failing. As long as they’re trying new things, developing new ideas and fixing problems. Creating an environment where we can all safely try out new methods is key to being trusted. I know the team doesn’t want to fail, and for the vast majority of cases, wont fail – but when they do it’s cool with me. I’ve worked in teams where the slightest error is ruthlessly punished, and it stifles innovation completely. See this post for some other thoughts on this topic. [BIZLIB]. Obviously we have to ensure failure doesn’t become a habit or a default outcome, but a good team will self-police this.

Trust vs Control – do big organisations get it right?

These days, many firms are super-highly regulated. The price for misdemeanors from non-trustworthy people is high [RTRAD], for the individuals and the firm. So you’ll probably have a LOT of governance. Mandatory training, compliance checks, risk reviews, market conduct – the list goes on. And sometimes it seems we spend too much time on governance, and not enough actually getting things done. I’ve heard it referred to as a source of frustration at a number of places that I’ve worked.

I’ve got a mixed view on this. The key risk and governance items are absolutely required, and often mandated by regulators. So we just need to get on with them. Automate where possible and seek to optimize. JFDI. However there are times when restrictions do seem influenced by a lack of trust. E.g. rejection of conference presentations because someone, once upon a time, did a bad job. Or blocking social media sites by default meaning we can’t access handy training resources e.g. SlideShare, YouTube etc.  Or excessive scrutiny of expense claims in case someone hasn’t followed policy. Even dressing appropriately for the workplace. All of those are not a problem with the right person. A trustworthy professional knows not to display client information in their presentation. They know not to be updating their Facebook page whilst on a conference call. They know the guidelines regarding expenses, and they certainly know not to wear their favourite Metallica t-shirt in a client meeting. 🙂 If they don’t, then they’re not the calibre of person your organisation needs.

So should we be concentrating more on hiring the right attitudes, rather than tarring everyone with the same brush? For sure it would be cheaper to have genuine trust in people rather than implementing complex controls [FORBES]. Let me know your thoughts in the comments.

Ok that’s it. Thanks for reading.

Supporting references

[HBR] https://hbr.org/2019/02/the-3-elements-of-trust

[QA] http://qaspire.com/2010/07/21/5-ways-to-build-trust-lessons-from-a-conversation/

[WNEXT] https://whatsnextpodcast.libsyn.com/rising-up-against-the-diminisher-with-liz-wiseman

[BIZLIB] https://www.bizlibrary.com/article/bizlibrary-values-freedom-to-fail/

[RTRAD] https://en.wikipedia.org/wiki/List_of_trading_losses

[FORBES] https://www.forbes.com/sites/keldjensen/2014/12/08/control-is-good-trust-is-cheaper/#518fc721322f

Accelerate your career with a Personal Board of Directors

Posted on by
Reply

Hi all,

As we wrap up annual performance review season, you’ll all be on the receiving end of feedback. Some of it will be good, some of it will be less so, but hopefully it will all be constructive. With any luck there won’t be any big surprises in there, that’s always unpleasant. Feedback should be a continuous process throughout the year, driven by the individual.

A great way of creating that pipeline of continuous feedback, advice and support is to think of yourself as a company. Banoub Inc. if you will. Has a nice ring to it actually. The best companies operate with a solid, skilled and experienced Board of Directors, working together to provide the direction that the company needs. No one person can do it all themselves.

And that’s the same with you. We all need our own Personal Board of Directors. The people that can advise, critique, praise, motivate and generally steer each of us through the minefield that is our career.

I like to think of my own Personal Board of Directors as 6 – 8 people that connect with me in a number of ways. Here are a few suggestions.

  • A Subject Matter Expert

    • Someone that knows my subject area inside out. A person I can learn technical and job-related skills from. A real expert in the field.

 

  • The no BS advisor

    • We all need someone who gives it to you straight. Someone who’s opinion comes with no BS. They’ll tell you how they see it, whether it is uncomfortable for you or not. Often a great way to get the feedback that others are too scared to give you.

 

  • A super-fan

    • Some people just like you. They might like the way you work, or your attitude, or you just click. It’s always good to have a positive fan on your Personal Board of Directors. They’re handy for spreading that positive message about you and for selling your achievements.

 

  • A critic

    • While your super-fan will tell you all the things you do well, it’s good to balance that out with someone who will let you know where you’re going wrong. They might seem negative, but if they’re spotting flaws that you are missing then they’re extremely valuable. Obviously attitude is key here; you want feedback to be constructive.

 

  • The connector

    • We all know someone who seems to know everyone! They’re all over your social feeds, all over forums and events. Their name crops up everywhere and they seem to get all the info on what’s going on. It’s great to be close to someone who has this profile. They’re able to connect you with people from all over the place and they open so many doors. And as cliche as it sounds, it really is all about the network.

 

  • Someone from Generation-Not-You

    • Your perspective on life is profoundly influenced by your generation. And there’s not a whole lot you can do about that. I like my Personal Board of Directors to feature someone from another generation. Be they younger, or older, they see things through a whole new lens and as such can offer an invaluable opinion.

 

  • The non-work advisor

    • I find it useful to have an advisor that I don’t share any real work connection with. Maybe they share the same hobby as you, or have similar life challenges, the non-work advisor can offer unique commentary that you can use to make real progress.

 

Finally I like to think how I can act as someone else’s board member. Maybe you’ll have a mutual arrangement with some of your own advisors? But do consider how your own skills can be of use to acquaintances at work. The recipient might not even realize you could be of use. So offer!

You’ll probably already have some of these roles already filled, maybe without even realizing it. And just like a real company, there will be turnover, hirings and firings, and maybe the odd scandal, but the group will undoubtedly provide a great deal of collective value.  One thing is for sure, your Personal Board of Directors will provide a continuous fire-hose of actionable feedback and advice, that you can use to shape your career for the better. Don’t rely on the usual feedback channels, go out and get hiring!

Regards, Paul

What to name your Tableau Server?

Posted on by
Reply

Hello all. Yes, contrary to popular belief, I did indeed survive Tableau Conference 2017. I’ll admit it was a close thing, but I got through it!

Now back to business..

This one all started with a tweet from my good pal, the Wizard of Excel (and Tableau genius) Mr Dan Harrison (@danosirra) who was wondering what to name his Tableau server host.

This awakened the server admin in me (not that it’s ever asleep).. It also made me question Dan’s taste in music.

An example being…

And this is the point. Server naming is critical in any organisation, large or small.

Picture the situation – you get woken up at 2am by an alert or a call from an operator – server “superman” is down. Fine if you’re experienced and know the environment inside out, but what if you’ve only just joined the company. You know the servers are named after superheroes, but that’s it. Was the production server superman or spiderman? Or was it WonderWoman? Do you need to take action? It’s not clear and you need to dig into a server inventory system to get more info, and that takes time. And you’re new, so you can’t remember the URL for the inventory system.

You assume superman is your production server. But it’s not reachable via console, and you need to call someone to get into the datacenter to fix it. So you call the hardware team – sure they’ll go in, but they need to know if the server is in the London or the Birmingham datacenter? Errrr…

So you dispatch Server 5’O to fix the box, and then the next day you find out it’s a development machine and could wait. What a waste of time.

So you get the problem here. It’s very tempting to name servers after Simpsons characters or animals (I’d choose sharks obviously), but those names convey no organisational information and as such, are useless.

So what should you do?

There are tons of different naming conventions you can use. Here’s one that I like

When I get that call in the middle of the night I (or the hardware technician) will want to know..

  • Where is the server?
  • Is it production, Disaster Recovery, UAT or development?
  • What application is it? Tableau, obviously.
  • Which worker of my Tableau cluster is it?
  • What operating system is it?

So I get called and am told server lnpwtsw3.company.com is down. Let me think..

  • ln – London
  • p – Production
  • w – Windows
  • ts – Tableau Server
  • w3 – Worker 3

And with that info, I know it needs acting on now, which platform admin to call if it’s an OS issue, and where to send the hardware technician if it needs physically addressing. I also know which worker it is so what the potential impact to my cluster is.

Yes the server name is a little harder to remember, but that soon comes and it is possible to create a DNS alias to reflect a friendlier name if needed. There’s also a balance to be had in terms of character count etc.

Another example – this time server name is lndwtsw1

  • ln – London
  • d – Development
  • w – Windows
  • ts – Tableau Server
  • w1 – Worker 1

Fine, that’s development. I’ll go back to sleep and deal with it in the morning.

So as you can see, it’s pretty important. Not just for me and my Tableau environment, what if you’re a server admin in charge of 5000 servers across the globe? This needs to be right!

Anyway, that’s it. Pretty simple. For the record, Dan made his choice…

See you next time, Paul

Data driven interviewing with Tableau

Posted on by
1

Hi

Continuing the series of posts where I explain how we are building an enterprise grade Tableau Centre of Excellence.

Here at Vizninja towers we pride ourselves on knowing Tableau & data. After all, we need to be able to add value and help users with their myriad queries.

So when we get the chance to hire, it is critical that we get the correct people. People with great skills in Tableau, data & visual analytics. People that can tell stories and make data come to life. People who want to help others see and understand their data. And being a data driven team we use data and visualisation to help us make the selection.

Our interview process goes like this.

  1. An initial screening call with the Agile BI service manager (that’s me!)
  2. A technical interview with the team
  3. An exercise involving Tableau Public
  4. A final chat with the big boss (that’ll be me one day)

Some more detail on a couple of these steps.

 

The Technical Interview

We have a series of technical questions that the team asks each candidate. The questions are split between Tableau Server and Tableau Desktop and also categorised in terms of complexity – e.g. Level 1, Level 2 & Level 3, (see here) with the more complex questions being at L3 level. So I wait until my team are in a bad mood and then I let them off their leash at the candidate….

Our interview viz. Created by @jakesviz

Click the image to get a better view of the tooltips. Apologies if they’re not so clear. Here’s what some of them look like. So we can see the exact question asked, points achieved and any comments.

On the dashboard, you can see the questions asked, the max points available per question and then the points attained per category and complexity. At the end we spit out a KPI that gives us some indication of a candidate’s capability. Note that a low score doesn’t necessarily indicate that a candidate is unsuitable. Often we see people who are super-skilled in Tableau Desktop but not experienced in Server (as in this case). A few weeks with the team will soon change that though. Our job is to create all-rounders in all aspects of Tableau.

So if the data checks out then the candidate moves on to the next stage.

 

The Tableau Public Exercise

For the next test we ask a candidate to choose a dataset from these public datasets and then create a viz on Tableau Public. The candidate then presents their viz to us and we look for the following

  • Good visual analytics best practice
  • Ability to create an engaging story and develop insight
  • Structured design process and ability to justify design choices

And if they’re really unlucky then @jakesviz will download the workbook and rip it to bits in front of them! Yes we are looking to see if you’ve commented your calculated fields!

Here’s what Jakub Jaros came up with..

https://public.tableau.com/profile/jakub.jaros#!/vizhome/SignigicantVolcanicEruptions/Main

Nice work huh? We thought so. So now you know where to go for your volcano information. This is a really important part of the interview process as the candidate presents their work to us and it can lead to discussion, debate and even argument. But it really gives a sense of whether someone loves dataviz and you sure need that if you want to work for me. We plan to add some data points to this stage so that we can come up with a final rating for each candidate.

After this, it’s a final chat with the big boss and hopefully a role with the team. And that’s when the fun really starts!

This approach has really resonated with senior management and as a result we are helping several other teams to adopt a similar process.

So there you are. That’s how we ensure we have the correct people to deliver a great service. Feedback appreciated in the comments.

Cheers, Paul

What we got wrong building our Tableau service

Posted on by
4

Hi

I spend a lot of time talking to other companies about how to put together a decent Tableau Centre of Excellence. And that’s cool. I love to help people and I also learn a ton from all the other great setups out there.

But that also gets me thinking. We are far from perfect. And we made a whole lot of mistakes on the way to building our service. So instead of talking about the good stuff we did, I thought I’d highlight what I think we got wrong.

So in no particular order of importance, here are our top mistakes

Onboarding

So you’ve done the demo, shown the capabilities of Tableau and your audience is wowed. They want it and they want it NOW! So how do you get them from wanting to having?

Well we didn’t do so well. Our purchasing is handled by another team and the process is fairly complicated. Our mistake was not building a solid enough relationship with the purchasing team early on and making an effort to understand the points of the process that could be improved. We kind of just let them get on with it when we could have offered more assistance. This meant that on occasion users had to wait up to 2 months before they actually got their licence! And sometimes that cost us users, who gave up during the process.

Eventually we got together and helped the purchasing team out. And now things are a lot better. My advice – if you see a team you have a dependency on are struggling, then speak to them and help them out. Sounds obvious, but on this occasion we didn’t.

Setting Expectations

I spend a lot of time talking to users, often at a senior level, asking them to feedback on their experience with Tableau. On the whole it’s great stuff that comes back, but occasionally I used to get surprised with users informing me that their experience was poor. Tableau didn’t do what they wanted, it was inflexible and hard to use.

That didn’t sound like the Tableau I know and love. So I did some more research and it turned out that the users who didn’t like Tableau were trying to get it to do something that it wasn’t designed for. Now that’s fine if you’re Allan Walker or Noah Salvaterra but most of my users aren’t that level – in fact few people are. And of course that meant the users were getting frustrated.

I think the comment that really resonated was “Tableau? That’s Excel online isn’t it?”. Er – NO IT ISN’T!

The problem was obvious. Users thought Tableau was something it wasn’t. And naturally they would get a degraded experience. So we created a document that clearly states what Tableau is good at, and what it isn’t good at. We make users read this doc when they sign up for the service so they know exactly what they are getting.

This was very successful and really cut down the instances of poor feedback.

Some related posts on this subject from Dan Murray, Matt Francis & Peter Gilks

Training from the Get-Go

I’m a self-learner. So is my team, and most of the people I work with. I’m sure you are as well, that’s why you’re here reading this. And as a result I expect others to be the same. And for the self-learner, the world of Tableau is great. Tons of bloggers, forums, help articles, Tweeters, online videos and all sorts of quality learning materials. It really is one of the strengths of Tableau IMHO.

So we created guides & 101 pages etc and told users to go and help themselves. And to be fair, some of them did. But not as many as we’d have liked. And as a result we got tons of newbie questions and consequently poor quality content on our server.

About 8 months into the service we decided to implement a structured, instructor led training programme, amongst other training initiatives. More details here. Much of the syllabus is covered by Tableau’s own online videos and other resources but for some reason, new users really responded to this structured course. As a result we saw a corresponding improvement in the quality of published content and a reduction in the basic level questions to the team. In hindsight we should have implemented this right at the start, rather than assuming everyone would be keen to self-learn.

Commercials

Much as I love Tableau, their commercial operation isn’t the most flexible. That’s not just my opinion, it has been mentioned in Gartner reports. As a result we’ve struggled to negotiate the most competitive packages that we could have done. There have been some valid reasons for that but I don’t think we put as much effort into resolving the related issues as we should have.

And that’s important. I don’t want to get the best price for the sake of it, in big enterprises there are a lot of competitive threats from other tools. If Tableau isn’t competitive with pricing then the people that make the technology decisions will be perfectly happy to rip it out and replace it with something else. Not what anyone wants.

Again much of this is down to relationship building. As our relationship with Tableau has grown, we’ve seen improvement in this area.

Gamification

I’m a big fan of gamification. It can really boost engagement and turn a good initiative into an awesome one. We’ve had a couple of half-hearted stabs at competitions, to try and get things going but there is so much more we can do. Hackathons, viz games, competitions and internal Iron Viz – we’ve got a ton of ideas but never made it happen yet.

I think that’s partially down to the wide geographical spread of my user base. It would be really hard to get people to show up in a particular location. Users are also insanely busy, would I be able to round up enough people to make it worthwhile? So lots of excuses and not a lot of achievement in this area. I’m open to ideas if you’ve got this one nailed.

That’s it for now. There may well be a part 2 to this as I’m sure there are more things that will come to mind as I cry myself to sleep thinking what a mess we’ve made of it all… 🙂

Thanks to the awesome Matt Francis for inspiring this post.

Happy vizzing, VN

The Three Levels of Tableau Support

Posted on by
3

Hi all,

Let’s talk a bit more about how to build a top Tableau support team. This post focuses on the support my team provides to our user base. At the moment we have just over 1000 Tableau Desktop users, and approximately 8000 active users on the server every month – that’s a lot of demand for our services.

Now users can be a pretty demanding bunch, with myriad questions, queries and problems. And we are busy. So how do we ensure that users get the level of support they need? Well we provide 3 levels of main support, with the objective being to ensure that the type of user query / issue is directed to a channel that gives it the appropriate level of attention. This ensures an efficient use of my team’s valuable time, and critically it cuts down the traffic to our email inbox which is always a good thing.

screen-shot-2016-11-22-at-14-45-32

Some of the support options for our users

Level 1 – Man down!

Red alert! Something is busted and it needs to be looked at now! For this we need any incident to be logged in a trouble ticket system, with appropriate priority and detail. We use Service Now for this (many other tools available).

So if users think Tableau is broken or they need some immediate help then they log a ticket. This is mandatory. We need to track and log the progress, and the data is audited regularly. No ticket, no fix. We obviously don’t wait stubbornly for the ticket though, if there’s a big issue we investigate while the incident is logged.

Once the ticket is logged it flows through our regular support flow. First my Level 1 team will take a look and see if there’s an easy fix. If they can’t fix it then it’s an escalation to my more skilled Level 2 team, and then a potential escalation to my main Level 3 team for the trickier issues. There may be a future post coming about effective incident management, so I won’t go into detail here.

Some users don’t like us mandating that they raise an incident ticket. But it’s the only way to ensure traceability of problems.

Level 2 – It can wait

Sometimes users have problems or requests for assistance that are not so time sensitive. Maybe a development dashboard has broken, or someone needs help from the team to perfect that Pareto chart, or hey – maybe they just wanna talk about how much they love Tableau (it happens!)?

screen-shot-2016-11-22-at-14-48-33

Book your appointment with a Tableau Dr.

That’s where a Tableau Dr. Session is needed. We dedicate 3 half days a week to Tableau Dr. Sessions. Users log onto our community page and can book their session from a list of available slots. If the next slot is in a couple of days then they have to wait to be seen. Providing this structure to the sessions is critical as it allows my team to keep control. Before we implemented the structured sessions we were getting peppered with do-it-now requests for Dr. Sessions. That meant my team was context switching all over the place and other projects were being impacted.

Providing structure also makes users understand this is a finite resource and thus they are more appreciative of this dedicated time with my Tableau experts.

 

Level 3 – Let’s talk about Tableau, baby

Next level of support is for general chat. Could be a question about functionality, or a point about performance, or a geeky joke, or someone just wanting to ask a question about our upgrade strategy – could be anything really.

 

That’s where our Lync Group Chat comes in. We’ve generally got a couple of hundred users on the chat channel at any one time so it’s a decent forum for such questions and banter. It’s great for my support team to see a question get asked, and then before we have a chance to pick it up, another user has provided the answer – a self healing community – IT support nirvana!

screen-shot-2016-11-22-at-14-45-08

Wanna chat Tableau? Use our Group Chat

 

What’s in it for me?

These support options ensure that each query gets an appropriate response. If it has all hit the fan, then we act quickly. If it needs more care and detail, then we book that time, and if it just needs someone to talk to then we’ve got a community of people ready to give that data hug. It also means we get hardly any emails. And email is a dreadful means of logging an issue, as there’s no traceability or feedback. Users only get annoyed when they feel a query is being ignored, and ensuring the correct channel for a query means users get feedback as appropriate and aren’t left wondering where that email question went to.

Also my support team can plan their work and aren’t constantly context switching, one of the biggest enemies of productivity.

So that’s it. Pretty simple to implement but mightily effective. As always, ping me if you want a more detailed run-through.

Happy vizzing, Paul

Tableau on Tour Keynote Speakers – Some Suggestions

Gallery

Posted on by

This gallery contains 32 photos.

Hi all, I love the Tableau Conference. But I also have a lot of fun at the smaller “Tableau On Tour” events. In particular I love the keynote speeches. We’ve had some crackers recently, with particular recent favourites being Tim … Continue reading →