An often neglected success factor in scaling agility is strategically connecting the big picture view across the organization. Teams gravitate to working in functional silos with independent and uncoordinated workflows across people, processes, and products, causing low business outcome predictability (<50%) due to poorly defined roles and disconnected collaboration.
In this webinar, we will highlight the differences between organic and intentional collaboration and why when collaboration is not strategically architected, predictability, visibility, and governance suffer as a result.
We will show specific use cases of how Slack messaging-driven collaboration and specifically its integration with your large work items in a tool like Atlassian enables business process automation, decision automation for effortless process automation, visibility, and productivity.
Building Customer Feedback Loops: Learn Quicker, Design SmarterTechWell
Similar a Slack + Atlassian Integration: Use Automation to Remove Organization Silos and Build a Collaboration Hub for Different Functional Groups (20)
3. HOUSEKEEPING ITEMS
Audio is streamed through
your computer speakers, so
make sure your audio is on
and turned up.
The recording and slides will
be sent to everyone via email
within 24-48 hours after the
webinar concludes.
Submit questions any time
during this presentation via
the Q&A box on the bottom
panel of your screen.
4. OUR SPEAKERS
Matthijs van Leeuwen
@MattICE
Solutions Engineer
Cprime
Johnson Wang
@jdubs
Senior Consultant
Cprime
Alex Muir
@AlexMuir
Consultant & Moderator
Cprime
7. AGENDA
01 THE BIG IDEA: MESSAGE DRIVEN AGILITY
02 WHY YOU SHOULD CARE
03 SLACK + ATLASSIAN USE CASES
04 KEEP THE CONVERSATION GOING/Q&A
8. POLL QUESTION #1
Rate your company’s usage and adoption of Slack:
A. Interested in Slack but still primarily using e-mails
B. Using Slack for chat only
C. Most company communication and decision-making happens in Slack
D. Using sophisticated integrations in Slack for message driven agility
9. POLL QUESTION #2
Rate your company’s usage and adoption of Atlassian tools:
A. Interested in Atlassian but not using it yet
B. Using Atlassian tools out of the box
C. All or most company initiatives and projects tracked in Atlassian
D. Advanced reporting and sophisticated integrations in Atlassian
12. By using Slack with Atlassian - and positioning it
as more than just a chat tool - you will take
advantage of the agility to make faster and better
decisions while automating work.
THE BIG IDEA: MESSAGE DRIVEN AGILITY
13. Time savings of over 6 hours/ week (64%)
Improved Collaboration (86%)
Reducing manual tasks w/ automation (71%)
Improved Consistency (64%)
Supporting enterprise tool integrations (60%)
Improved response times (56%)
Source: 451 Research – “Digital Transformation Trends Driving Team
Collaboration and Productivity”
Collaboration
Improvement Cycle
Adapt to Change
Improvement Cycle
Deliver Value
Deliver Value
The Agile Mindset:
14. - Empathy
- Courtesy
- Thriving
- Craftsmanship
- Playfulness
- Solidarity
- Open company, no bullsh*t
- Build with heart and balance
- Don’t #@!% the customer
- Play, as a team
- Be the change you seek
15. - Free
- Pro
- Business+
- Enterprise Grid
- Cloud
- Free
- Standard
- Premium
- Enterprise
- Data Center
16. SLACK + ATLASSIAN: WHAT’S POSSIBLE
• Create a culture of transparency and collaboration
• Collaboration hub for the full tech stack
• Smart notifications for business updates
• Jira ticket transitions through Slack
• Assign work in Slack
• Custom event notifications
…And more
22. Without Slack
INCIDENT MANAGEMENT
Incident alerts sent to
shared e-mail inbox;
slow and
unresponsive
Who’s on duty? Triage
and ACK? Escalation
path? Impact and
remediation?
Context switching;
lack of visibility and
reporting
23. INCIDENT MANAGEMENT –
JIRA SERVICE MANAGEMENT
SLACK HALP
Monitoring & Alerting
Receives alert from
Prometheus and sends
to the right group of
people
Ticketing help desk
that creates a ticket
into Jira Service Desk
25. Without Slack
LEAD CAPTURE
New leads via shared
inbox; unstructured
information
New or existing
customer? Prior
engagements? Rates?
Who’s responding?
Lack of visibility into
sales notes, prior
SOWs, information
silos
26. With Slack
LEAD CAPTURE
SLACK
Sales team channel;
contextualized
conversations;
respond to customer
WORKFLOW BUILDER
Standardized form =
consistent data;
automated response
+
Unique JIRA issue
key; Salesforce data
pulled or pushed;
Sales assigned
+
28. Without Slack
SERVICE REQUEST MANAGEMENT
Shared email inbox
where key
information gets
lost in Reply Alls
Who’s working on
what? What’s the
progress? Was the
service good?
Lack of visibility
into utilization,
analytics, and
reporting
29. With Slack
SERVICE REQUEST MANAGEMENT
SLACK
Shared team/project
channel;
contextualized
conversations;
Threads
WORKFLOW BUILDER JIRA SERVICE DESK
Each request has a
unique Issue Key;
work is assigned and
tracked; reporting
30. KEY TAKEAWAYS
• Slack ♥️ Atlassian
• Integrate, standardize, automate
• Outcomes > output
• “Mean time to pivot”
32. KEEP THE CONVERSATION GOING…
• Connect:
• [ Alex Muir: https://www.linkedin.com/in/alexlmuir/ ]
• [ Matthijs van Leeuwen: https://www.linkedin.com/in/mivanleeuwen/ ]
• [ Johnson Wang: https://www.linkedin.com/in/jonccwang/ ]
• Check out Cprime upcoming webinars, read our blog, download whitepapers/case
studies & more:
• www.cprime.com/resources
• Share with us what topics you are interested in, ask us questions or give us
feedback!
• learn@cprime.com
33. FOLLOW US ON SOCIAL MEDIA
Share in the conversation & keep updated on
thought leadership, events & more!