Ever notice how you feel when you enter a company's doors? Is there excitement in the air? A buzz? Does it feel like innovation is oozing from the walls? Or does it feel as exciting as a tax man's trousers? What makes you feel these things? And how can you start creating a better cultural experience for your employees and customers?

Culture is hard to change. And every time I hear there is a "mindset problem" or, "we need to change our culture", it becomes painfully clear that focusing on process and tooling changes alone won't cut it. Thankfully, there are effective techniques to help you hack your culture.

In this workshop, you will learn how to identify the attributes of your existing culture. You will build a culture map, starting with the visible signs of culture and then delve into norms, values, and finally, the core of culture--the underlying assumptions we don't even think about. Understanding where you are, culturally, is the first step.

From there, you will run through facilitated activities to build a culture hack. Simply put, a hack allows you to test a culture change and if it works, you can stabilize that change and start adding new hacks. Each hack moves you down that all important path to a new, vibrant culture, step by step.

My team has been experimenting with these techniques with several organizations. You'll hear about some real-world hacks and how they helped organizations improve. Our approach is not built on a single culture framework or a change management system. It is built on the work of many; the Cynefin framework, complex adaptive systems thinking, lean change, supported by culture walks, interviewing, and impact mapping to name a few of the tools you'll learn to use.

As a leader in your organization, one of your most important roles is as the steward and curator of your culture. This workshop will help you make culture change real, practical, and measurable. With these tools, you can have a positive impact on your people and customers.

Here are some common cultural challenges:

• Excessive command and control
• A belief that employees need detailed processes because they are incapable of making decisions on their own
• Fear of making a mistake
• Long and excessive approval processes - again, because employees cannot make good decisions
• No or little focus on customers
• Value statements like "We value our people" but with no supporting evidence
• Lack of employee engagement

Two years ago I presented the story of a client in the US who underwent a very fast and aggressive transformation. Although it was ultimately successful, along the way, we nearly destroyed it all. The saving grace was a small group of courageous leaders who made some tough decisions to get things back on track, and continued to drive the progress needed to succeed. The success story was presented at TAC in 2014 and the near colossal failure story was presented at Agile 2015. We bring this amazing story together into a single talk with many important lessons.

As more and more organizations adopt agile software development practices in large and complex environments, IT and corporate Finance teams are struggling to appropriately capitalize agile projects and agile product-based development. Existing organizational models and government regulations are based on traditional methodologies, which track capital and operating expenses of discrete project phases, with clear delineations. How do you decide, measure and track these in an agile environment with delivery phases intertwined within time-boxed cycles? There are opinions, but at Deloitte, we have looked into this challenge and collaborated with our agile and finance experts to develop, test and implement solutions with clients.

In this talk, we'll share our point of view on the important considerations for accurate and appropriate capitalization in product-based organizations using process frameworks like Scrum.

Drop in to hear about what we've done and get some ideas on how to move forward with your own capitalization challenges.

The approach is simple, but more importantly, has been tested in the real world.