Lucidchart Connect Phoenix: Context is Key
•Download as PPTX, PDF•
0 likes•137 views
Lucidchart users, partners, industry experts, and team members gathered in downtown Phoenix to learn, be inspired, and network with one another. One of our guest speakers was Kevin Allen, Technical Account Manager at Atlassian. Kevin talked about the importance of visual communication and how a picture is worth 1,000 words.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Lucidchart Connect Phoenix: Context is Key
Similar to Lucidchart Connect Phoenix: Context is Key (20)
More from Lucidchart
More from Lucidchart (20)
Recently uploaded
Recently uploaded (20)
Lucidchart Connect Phoenix: Context is Key
- 1. Context is Key How a picture is worth far more than 1,000 words
- 2. Introduction Kevin Allen Technical Account Manager Atlassian
- 3. Context Is Key ● TAM, a day in the life ● Context ● Picture this [Insert image]
- 4. A day in the life of a TAM ● Apps ● Complexity ● No Easy Answers
- 5. A plugin by any other name should smell so sweet ● Plug-ins, add-ons, apps ● DC Apps program ● How we validate ○ Installs, reviews, future proof
- 6. Break it down for me
- 7. LMGTFY ● There are no easy answers ● Ask a question vs. solve a problem ● Help
- 8. Context ● Show me how to… ● 5 Whys ● Visualize the problem
- 10. No workflows Validate the process Periodic validation What’s missing?
- 11. Who cares? How are they connected? Understand your customers Keep it up-to-date
- 12. Your diagram is already out of date
- 13. The Federal Risk and Authorization Management Program (FedRAMP) is a government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services.
- 14. FedRAMP
- 15. What’s your DoD?
- 17. Keeping up with your users in a changing landscape Future proof Solutions should be available where your users are Does it make life easier?
- 18. Context is Key How a picture is worth far more than 1,000 words Thanks! -Kevin
Editor's Notes
- Here’s the basic outline that you should follow: Title slide Intro (speaker bio/company intro) (1 - 2 mins.) Main content (15 - 20 mins.) Q&A (5 - 7 mins.)
- Yes that’s an Atlassian Certified Professional hoodie - former enterprise admin and solution partner Yes that’s me on the Millenium Falcon, no I can’t tell you how that happened Yes, I do want to be Han Solo when I grow up
- Ultimately I’m talking about diagramming but I’m sort of a story teller so let’s get started
- WTH is a TAM - technical account manager, largest 100+ customers, subscription (yes, people actually pay to hear what I have to say, I feel like I need to pay at home, so I guess that’s my work life balance) A few of the things that I encounter regularly that overlap with our purpose today
- Apps - don’t even get me started DC Apps - more testing and security requirements - more changes coming here stay tuned TAMs and Apps - *details *committee (if time allows) *iterate (abc - always be curious, what’s new, what features are you missing)
- This is a cross section of what TAMs deal with daily, not all of it at once, but that’s the ground we cover
- If it was really easy we wouldn’t be talking about it How can I implement this? 99% of the time “why would you want to?” AUG, Community, WAC, CAC, JAC, Partners, Support, TAM, and of course Vendors
- No, explain why it’s important, who is driving it, what outcome are they looking for Why, why, why, why, why When in doubt, draw it out!
- I already said don’t bring me a workflow, but this is perfectly acceptable! Documenting your process is even more important as technology continues to evolve, validate that what you think is happening is truly happening and challenge the old ‘reasons’ Set a timer on this process - give it a Jira ticket and a due date for review, set some filter and move on POP QUIZ - Where’s the feedback loop to HR?
- Earlier we talked about who cares, why is that important? Wouldn’t it also be important to know who they relate to or report to?
- Basically take the guess work out of secure approved SaaS purchases for government entities
- Does it include documentation? Does it include imagery? Should it?
- Don’t ever underestimate the power of visualization particularly when you’re trying to illustrate Scale or Complexity
- Here’s the basic outline that you should follow: Title slide Intro (speaker bio/company intro) (1 - 2 mins.) Main content (15 - 20 mins.) Q&A (5 - 7 mins.)