"Salesforce Spring 21 (SP21) Starts From April 2021" Join our Channel for latest Updates https://t.me/salesforcekeeda

Tuesday, February 9, 2021

Thought process /Client Communication questions:

 These questions will be asked to understand how to communicate with clients, how you build and maintain relations with them.

 113. Given a scenario where we have multiple stakeholders for a dashboard, how to you interact?

 If a dashboard has consumers at different levels, example CEO, regional manager, and field staff, I try to meet and get requirements from them individually given that every individual role will have specific business questions to answers.

 Every role has some specific KPI’s to look at, specific business questions to answer, specific data to analyze, display and granularity of data detail. There is no one size fits all. It’s a good practice to tailor dashboards as per client requirements. 

114. Do you tend to create multiple variations of the same visualization for different stakeholders, if yes why and no why, what’s the rationale behind that?

 I believe that if we are speaking to everyone, we are not speaking to anyone. There is no solution that fits everyone’s needs. If you create one dashboard for all the consumers in the company, no one person will benefit from it. 

The solution has to be customized to fit the needs of the consumer. The more we can understand their needs, the better we can build a solution to solve their problems.

115. How do you enable reports access for both internal and external customers?

 We design and use a combination of row level security, custom tables, roles and permissions to enforce the required security for customers. That will be an architecture and server level discussion we would have with our internal team, internal and external customers and design a best solution that fits the need.

 116. How do you design architecture to be both secure, scalable and robust?

 It depends on various factors like the number of users who are going to interact with dashboards, user roles, user types (both external and internal), the server model (term or perpetual), licensing model (core based or user based) etc.

 117. How do you communicate with stakeholders and how do you form relations?

 The key thing here is to understand client’s requirement and make sure we design and build dashboards to solve the problems. It’s always recommended to keep client’s in the loop of what’s going on in the project and be up-front if there is any change in the project delivery. Client doesn’t like any last-minute surprises.

118. How do you set and manage their expectations?

 a) Be Honest from the get-go.

 b) Set goals, and point to these goals during every single conversation.

 c) Under- Promise and Over-Deliver.

 d) Constant Communication

 e) Weekly/ fortnightly status reporting.

 f) Be transparent about what you can accomplish 

g) Be upfront about what happens if plans change 

119. How do you capture requirements?

 We capture dashboard/report requirements in a business specifications document, technical specifications document (high level and low level), wireframe, storyboard, user stories etc. You can read more here.

 120. How do you capture business questions, what to be solved? 

Those can be captured as user stories. Each business question that needs to be answered is captured here which forms as a foundation for dashboard design and building.

 121. How do you communicate with clients when there is delay or issue that impacts delivery?

 It is highly recommended and I follow swift communicate with the clients as soon as I have visibility of the change or slip in the schedule. This ensures both of us are on the same page and client can make changes/ inform their customers in case of any business impact. 

122. How do you convince and make clients understand about technical stuff or benefits of a particular design choice?

 I always show them visually by creating a quick proof of concept and explaining the benefits of a new approach if that is the way to go.

123. How do you roll out delivery across the whole organization?

 We identify a few power users who understand the business well and showcase and train them first to make sure they understand the benefit. Once they are comfortable with the solution, they can help the people in the field in their respective regions to adopt the solution. We also identify and release the solution phase wise so it is easy for us to support new requests and user questions if any. 

124. Is documentation process important in the project?

 Yes, it is absolutely necessary to have proper documentation for a few reasons below. 

A. It will be easy for other/new team members to pick up the report and make changes if needed.

 B. This serves as a document for auditing and change control purpose. 

C. This can be used to refer when impact analysis of a new change (adding a new field, removing, changing etc.) is raised. 

It’s wise to use tools that document the workbooks saving a lot of resource time and more efficient in capturing all the details.

 Rapiddox is a brilliant tool that does Tableau dashboard documentation in seconds. 

125. How do you make sure the branding is consistent throughout the delivery? 

We follow the company specifications including logo, colors, formatting, font and any other branding materials to make sure the dashboards are all consistent across the board. We try to specify everything in a document for everyone to follow.

 126. How do you communicate with stakeholders during the design and building of dashboards? 

We usually have a weekly showcase with the stakeholders and the team to present the report, brainstorm, seek feedback and iterate the changes to make sure we are on the right path. 

127. What is the difference between showing data and storytelling data?

 Showing data is all about presenting data as a self-serve analytics dashboard for users to explore and find answers. Here we are not presenting any key takeaways for action, but giving them the power to analyze data.

 Storytelling the data is about we, analysts doing exploratory analysis to find story in the data and presenting the facts to the stakeholders to understand quickly and easily that prompts an action for them to make a better decision.

128. Did you maintain server administration, users?

 Yes, I did maintain tasks server administration to perform tasks such as but not limited to adding new users, maintaining users, Active directory configuration, SSO, licensing, creating and modifying schedules, installation of new server instances.

129. Did you ever lost your hold on best practices and compromised to follow what client says?

 Sometimes we have to follow what client insist regardless of they are standard data visualizations or not. It’s common. We try to explain them the pros and cons of the process, but it is up to their decision to tell us what to follow.

 130. Did you ever receive any out of the report requests and how did you prioritize?

 We do receive ad hoc reporting requests from various teams time to time. We do receive, we will politely ask them to route them through our manager so he/she can assign the work based on priorities. 

131. What 3rd party tools have you used in the Tableau/Data visualization project?

 We used: Rapidox for workbook documentation.

 Tabjolt for load testing

 Powertools for Performance tuning and best practices.

 Tabmon for Performance monitoring. 

Tabmigarte to migrate data between multiple environments.

 Read more here and here.