The numbers speak volumes: High performing IT organizations are two times more likely to exceed productivity goals, according to Puppet Labs 2015 State of DevOps Report. They also experience 60x fewer failures and recover 168 times faster.\nBut what makes an IT team \u201chigh performing?\u201d What practices do the very best teams follow to become more efficient, collaborative, and responsive?\nWith more than 68,000 customers (and millions of IT and DevOps users), we\u2019ve learned a ton at Atlassian about what separates the best from the rest. Here are our top tips.\u00a0\nHigh Performing IT Teams Put Culture First \u2014 DevOps Style\nProcesses and performance metrics are important. But the most effective IT teams focus first on their culture and how they work together both within and across teams.\nOur biggest tip? Draw inspiration from DevOps for practices that increase team collaboration, transparency, and trust.\u00a0 Daily standup meetings are a great way to track progress and priorities and reinforce the team dynamic. Use retrospectives to keep getting better.\u00a0 And at Atlassian, we use chat and video conferencing in place of email \u2014 resolve 50% of all IT requests even faster by gathering the right people in a HipChat room in real time.\nFor extra credit, hold \u201chack days\u201d \u2014 or marathon days of intense collaboration and brainstorming where the team comes up with new ideas to improve the organization and the business.\nThey Automate Themselves Out of Their Own Jobs\nIn DevOps, the very best teams make it their mission to find new ways to use automation to make their own roles obsolete.As a reward, they\u2019re moved to bigger and more exciting roles \u2014 each time with the same goal of automation.\nAt Atlassian, we use JIRA Service Desk to auto-triage email requests \u2014 using powerful automation to properly prioritize tickets, assign them to the right queue, auto-approve small purchase requests, and escalate urgent SLAs.\nEncourage your team to constantly find new ways to embrace automation, eliminate repetitive work, create repeatable processes, and provide better experiences for customers. Instead of manually triaging and following up on every ticket, challenge them to let the tools do the work so they can get more done.\nThey\u2019re Lean (And Always Getting Leaner)\nMove quickly, be scrappy, and be agile. \u201cLean\u201d service management is all about eliminating duplicate work, unnecessary administration, and bloated processes to create a more simple, scalable environment for continuous improvement.\nTake change processes, for instance. Rather than creating \u201capproval monsters\u201d where each type of change follows a dramatically different set of complex rules, the best teams today are switching to dev-ops style peer reviews instead. In this model, all proposed changes must pass a peer review before going straight to testing and production. It\u2019s a faster and far more reliable way to vet changes and eliminate complexity at the same time.\u00a0\nFinally, continuous improvement and failure go hand in hand, so set up your IT team to absorb failure, recover, and learn from it.\u00a0 Post-incident and post-mortem reviews ensure your team members don\u2019t burn themselves out fighting the same issues over and over again, and instead focus on resolving and prevent recurring problems altogether.\nThey Keep Track of the Metrics That Matter\nResist the urge to measure everything, and look instead for ways to set meaningful measurements that support company and organization-wide goals.\nFor example, some teams have a big push to reduce call times. Time is money, after all. But it often makes sense to encourage Level 1 support to stay on the phone longer and gather more information, since Level 1 support calls cost $12 - $22.50 on average, vs. $45 - $100+ for levels 2 and 3.\nThe best teams don\u2019t obsess over every small number: they create a balanced scorecard to track their overall performance against the metrics that matter most to the org and the company \u2014 like mean time to repair (MTTR), number of repeat issues, cost per incident, and performance against operational SLAs.\nFor extra credit, set joint goals with your business stakeholders that align to corporate priorities. This brings you closer to other teams, and ensures accountability against a common company vision.\nThey Share Success\nFinally, truly high performing teams take the time to celebrate their successes and give kudos to other employees for doing great work. At Atlassian, any employee can reward another employee with a small \u201cthank you gift\u201d automatically via a simple JIRA Service Desk request \u2014 which strengthens our culture of collaboration and communication even further. Our takeaway? Build a culture of collaboration and continuous improvement. At the same time, get rid of legacy tools that are causing you to work harder, not smarter. Your business will thank you for it.\nInterested in learning more about high performing IT teams? We surveyed over 600 teams to find out what makes them tick. Find out\u00a0here.