Day 670: One door closes and another one opens

In late August, I completed my Master Black Belt. It's official, I'm done the program! I received the coveted Crystal Pyramid of PowerTM and was sworn to use my new-found powers for good and not evil (but would join Elon Musk in a bombing run to Mars if invited).

I was very happy to have completed the progam, but that last week was really mentally and emotionally exhausting. As a super procrastinator, I really topped myself, and was still finishing up my workshop the day before presentation (ssshhh don't tell anyone - ooops!). But I got through, and then immediately went on vacation. We all went to Toronto to visit with family, and I took advantage of the time away from work to think about "what next?" (and see a Jays game)

Conveniently, what was next pretty much fell into my lap. I had an offer to join an organization that needed my skills, that was growing, and that was in a sector that I adored (aerospace). So when I returned from vacation, I handed in my notice. It was in many ways one of the easier decisions I've had to make in my career, not because the current company doesn't have a lot to offer, but because I needed to do something dramatically different and to have a better work-life balance. So when this offer showed up, and it ticked almost all of the boxes, I jumped.

So today is my last day at my current organization. And as I walk the hallways with a giant bowl of candy, saying thank you and goodbye to everyone, I know I will miss everyone here. But I am also super excited about what lays ahead. And this organization could use the space that I will leave to fill it with new ideas, new people, new processes. 

Sometimes, we need to make space for change to happen. We do it in our personal lives buy cleaning out the closets, by dropping activities that don't mean much to us, by stopping doing certain things. I gave up Facebook over 2 years ago because it was not really contributing much to my life. I was putting time and energy into it and wasn't getting a lot of value back. Likewise, I'd had acquaintances that took time and energy and didn't give a lot in return, so I chose to not spend that time and energy in that relationship. By giving up on those time-wasters, I have more time for things that bring me joy - like coaching, like trying new activities and pushing my boundaries, like family.

So I leave Alpha hoping that I created at least a foundation for its future, that I left it in a better place then when I found it, and knowing that I am leaving space for future growth of its people.

AMac

PS: I will probably keep writing this blog, so stay tuned...

Day 628: So close I can taste it

This may be one of my last blog posts as I am officially in the home stretch of my Master Black Belt program. I am so close to the end of what has been a really interesting, challenging, fun, frustrating, complicated ride. By this time next week, I will have delivered my final workshop, presented my final presentation, and screened my final video (and yes, I'll post it on this blog once screened). It's all coming together rather quickly, and this pressure-riven procrastinator loves it...

After it all winds up, then it's time for a vacation. We'll visit family and enjoy a break before the school year starts up, before skating season kicks off, and before going back to work. 


I'm kind of starting to wonder "what's next?" even before I pass the immediate milestone in front of me.

When racing, I'd always be nervous about the "what's next?" question - and more specifically about the period of time between ending one journey and beginning the next. It may be the lack of focus, direction that makes me queasy. It may be the fear of not having some goal that I can talk about with others; most of my friends and family know I'm always up to something, so a lot of our conversations start off like "what crazy thing are you training for now?" What on earth am I going to talk about? The upcoming federal election? The MLB stretch and how the Blue Jays are playing? Hm.

I have never been good at rest, at relaxing, at unplugging, at being still. It is something I have worked at over the years, and made some progress, but it is hard work for me. It's when I have a goal on which to focus that I feel still - it's almost counter-intuitive. 

Good thing I still have a crazy week in front of me.

AMac

Day 611: House Painting (or why I should be working on my final presentation but I'm not)

Today I'm painting the house. We've been working away at repainting it since last summer. We did subcontract out a big portion of it, but there are a lot of sections that need repair or other fixes before even putting a brush to it. Plus being a heritage house (1908) there are a lot of features that, while charming, do require a lot more time and attention to not ruin. So it's a slow process. We want to do it right (and not break the bank) and there's something worthwhile in doing it yourself. At the end, hopefully we'll be able to look at it and say something like "damn that's a fine looking house."

Yet I'm three-ish weeks away from my final two presentations for my MBB program, and I've barely started. I should be using the entire day to work on them. I know this is one of my weaknesses - I like to have 90% of the solution/story/idea done in my head before I put pen to paper (brush to wood?).

I know it's not the best way to do these things, and I know it drives some people nuts. But here I am painting instead of sitting at a computer screen drawing a blank at what to type. I'm hoping (or betting) that the idea will come to me while working on something completely removed from the topics of my presentations.

Or am I just procrastinating? I've always worked like this on things where I need to be creative. If it's straight-forward items, like updating a document or analysis, no problem. Heck, if it's going for a 20k run up a mountain, bring it on, the creative side of my brain isn't needed. But for some reason when trying to be... clever? creative? I find I take a loooong time. I get it done, but usually right at the last minute. It's like the right-side of my brain needs to be under some pressure, some time-bounded stress to perform. I like it when something clicks together and the story presents itself, almost like magic.

I found this graphic from Mercedes-Benz that seems to resonate with me:

While I get some enjoyment out of the right-brain activities, quite a lot in some cases, a deadline does not motivate me any more than the activity itself. In fact, I'd feel pretty confident in saying that a deadline probably makes me want to drag my heels more than usual. 

So back to painting, while I wait for that magic moment when I see the story present itself.

AMac

Day 559: So close! Intern days done!

Yesterday was a BIG day for me as I finally completed the last required internship day for my MBB program! I spent two days at a local-turned-national retailer, working on a supply chain challenge, followed by one day at a regional food producer starting a lean assessment. And while I'm thrilled to be done this part of the program, I know I still have projects outstanding - some of which I'm not too worried or stressed about but one that is a BIG project for me and I'm going to have to make sure I git'er'done on time. Tick tock tick tock....

But back to these last two companies where I spent these days - I wanted to share an interesting observation. The first company, I'll call them Company A, had been on their lean journey a few years now. The second, Company B, hadn't even heard of "lean" or the concept of continuous improvement. Company A had a very clear problem to solve - they knew what they needed to address, perhaps not how. Company B didn't know where they were going, or even what was going on right now - they didn't even know what problems existed to be solved. Company A had staff who were motivated to solve the challenge, and who worked openly, honestly and together to get through to a solution. Company B was full of whispered hallway conversations, mistrust and fear. Company A knew their vision very clearly. Company B - no one knew one existed or was written down anywhere.

As I reflect back on the vast differences between these two companies, I am amazed at how far Company A moved the "culture needle" in a few short years, and while I think myself an optimistic person, I wonder if Company B isn't ready for real change, you know, the kind of change that requires an honest look in the mirror (so to speak).

In all my visits to all these various companies, there are many similar themes - we want to get better, we want to improve, we need to improve... our people are important, our customers are important, our shareholders are important... 

But the difference I see in those that do improve compared to those that don't is in the leadership of the organization - having the vision to see where to steer the ship, the courage to let go of control and trust their people, and the humility to understand that it's not about them (time to check the ego at the door).

AMac

Day 521: Easier to Coach than to Learn?

One of the things I do in my job is coaching. I coach people in different ways to accomplish different things - from visual management and organization to personal development and everything in between. One recent session was about helping people focus on how to manage upwards. It was in the context of the Gallup 12 - a set of twelve questions used to assess employee engagement (I wrote about it before, here). I asked everyone to look at the twelve questions and think about which ones were truly the responsibility of the organization and which had the potential for influence and action by the employee - that is, put effort where you have the ability to affect the outcome.

After the session, I decided to do the same exercise myself. And I was pretty surprised to see that in a lot of areas, I was doing a terrible job of actually taking action. Why was that? I knew the philosophy, the theory, the how-to, yet wasn't even doing it myself. Was it time or lack thereof? I don't think so. Was it desire or perceived need? This might be closer to the truth. 

It's funny how sometimes we don't take our own best advice. I live near a major hospital and am still baffled when I see doctors or nurses outside smoking. You'd think they would be leading by example, or at least doing right by themselves based on their knowledge and experience. I spend so much time and energy trying to grow or shape my career, my skills, but I completely missed this aspect of it - that for as much as I think I am doing a good job as a coach to those I coach, I am completely far less effective at coaching myself. 

It may be the hazard of the job. 

AMac

Day 493: When "CI" means "Control and Influence"

I am just back from Edmonton, after a three day White Belt kaizen session with another of our field service groups. This session was a bit unique in that this group was able to determine their own project instead of having a sponsor prepare a project for them. Lots of interesting ideas came up, but many of them involved people who were not in the room, not on the project team. In fact most of the ideas started out with "How about that process done in Toronto?" or "Maybe we can look at how we work with those guys in Burnaby?"

These were areas they had very little control over - half of their project time would have been spent trying to influence decision makers thousands of kilometres away. 

While interesting ideas, I wanted to see what the team could accomplish there and then. We went to gemba - in this case the warehouse and the field tech's truck - and looked. What wasn't working here? What wasn't self-guiding, self-explaining? What should this area look like? What was difficult? Unsafe?

So I let them in on a little secret - sometimes the "CI" in "continuous improvement" really means control and influence.

Deciding on what improvement to make, and at what level, success will depend on both: your ability to affect change because you control the process - you are the decision-maker; and where you don't control the process, your ability to influence those who do.

So with their new version of "CI" in their kaizen tool box, standing in front of a pile'o'stuff that made no sense to them, the light bulb went on. 

"We can fix this" they said.

And so they did. 

After a whole lot of 5S, they saw the end result and how the new standard made sense for them. More importantly, they saw how they owned this new standard - no one from any of the other offices had any real control over their solution. As long as it worked for them and the type of work they did at this location, it was valuable to this team. Even better, the new standard would act as an influence on the other locations who were doing similar work.

Best of all, the team could see the logical next steps - which projects to tackle next, which additional improvements could be made - all focused on the areas in which they had the greatest degree of control. 

AMac

Day 479: The Full-Circle Effect

Last week, I was lucky enough to participate - as a presenter - at the Burnaby Board of Trade's Green Talks! event. Five minutes on any topic about the greening of our business. I chose to talk about the major challenges we had in getting employees to care about waste sorting, about their commute, about the energy use at our facility. But I also showed how we slowly changed that mindset, and how after three years, the organization had achieved some impressive results. I talked about the need for branding, guerrilla marketing (quick'n'dirty/cheap & fast/funny), and communication. This was after all a change we were asking of our employees and we needed to do a good, no - great - job in communicating why we were making this change. 

Which is more effective?

A company-wide email stating something like "Effective immediately, all employees will sort their organics into the green bins in the lunchrooms" with the email printed and taped above the bins.

OR

The new green bins, each bin adorned with distinctive, highly visual posters and labels, with the company's green mascot clearly shown, and a real live friendly person standing there explaining how and why we will sort our organics to prevent them from going to the landfill, and who gives you a lollipop as a reward for listening and sorting.

(Yes, we really did this.)

Seems pretty obvious I think. If you really want people to understand the need for a change, you have to talk to them about it. One of the building blocks of Training Within Industry (TWI) is called Job Relations (JR), and one of the core principles of JR is that you tell people in advance about changes that will affect them.

Seems pretty simple right? So why are people so surprised when the company-wide emails don't drive effective change? Why do organizations keep doing it and expecting results? Isn't that the definition of insanity?

I think it's because sending an email is EASY. Putting in some effort to (1) lay the foundation for the change, (2) talk to people about the change, (3) answer their questions about the change, (4) encourage the right behaviour with praise/reward isn't hard, but it's not as easy as sending an email. I'm pretty glad that I work with people who are willing to put in the effort to do it right. So much so that we put it on our wall.

So from being able to show off our sustainability successes at this event, and being really proud of all that we had accomplished in a few short years, less than a week later I turn around and have my doctor (my respirologist) tell me that I have developed pollution-triggered asthma. That's right. All my years of running, triathlon, cycling, swimming, skating, all those activities and accomplishments didn't make much difference - the air I was breathing on a daily basis was causing my lungs to constrict and would have eventually turned into COPD if I hadn't pushed to have it checked when I did.

The irony of this whole situation isn't lost on me. 

I'm not certain what it means - for me - yet. But I'll figure that out.

AMac

Day 461: Is it about trust?

I like to try and keep my brain thinking thinking thinking, so I often will grab a book or magazine from my bookshelf - at random - and read an article or snippet, looking for a phrase or word or concept to spark something. So it was coincidence that I grabbed a book full of articles from the mid to late 90s espousing how the Internet was going to change ev-er-y-thing ("Creating Value in the Network Economy", Don Tapscott, Ed.).

The articles were well written, and quite interesting to read, being almost 20 years after initial publication. Some were bang on, and some, well.... some still hadn't come to fruition. One of these articles was about the Virtual Organization and Trust (Charles Handy, auth.), looking at what the new millennium would need to make the virtual organization a reality.

Wait a minute - lots of companies have people that telecommute, work remotely, work in completely different time zones and locales. Sure, but lots of companies DON'T. Why?

This article suggested it was about trust - and tried to outline what the author suggested were the seven rules of trust:

1: Trust is not blind
2: Trust need boundaries
3: Trust demands learning
4: Trust is tough
5: Trust needs bonding
6: Trust needs touch
7: Trust requires leaders

Now I'm not here to write about telecommuting, remote working and the virtual organization, specifically. I'm stating that I think that the seven rules of trust apply to all organizations - virtual or bricks'n'mortar. I see the effects of high-trust and low-trust environments in most organizations I visit, and sometimes both in one organization. I bet if you stop and reflect on your organization, you might as well. So let's take a deeper look at trust.

Let's look at the first one: trust is not blind.

How many of us work in an organization large enough or undergoing so much change that we don't know some of our fellow co-workers? Quite a few I bet. But hopefully we know the people we work with on a daily, regular basis. And once we get to know a new person, understand their role in the organization, we start to develop some degree of trust which hopefully grows over time. The organization I work for has a sister firm just south of us, which for a long time was seen as a black box of unknown-ness. We didn't know them, so we didn't really trust them. So after reaching out to my counterpart in that firm (about a specific issue) and establishing a basic relationship, we have been able to increase the level of trust and co-operation between us, between our teams. 

So I guess I'd agree with the premise that unless you can "see" the individual, it's pretty tough to just give over any level of trust to that person, and by extension their organization. So how does this apply to people we must trust in order to be successful? Like how we work with our supply chain partners? We have to develop some trust with those partners, who we don't usually see every day, we might only see them a few times a year.

Then there's rule 6: trust needs touch.

Touch doesn't need to be constant either - but frequent enough to be effective at keeping us out of the dark. The touch points also need to reinforce the trust, the relationship, and I think also the shared vision. It's a chance to ensure everyone is rowing at the same speed, the same cadence, and hopefully that we are all rowing for the same purpose or in the same direction. This one I like.

How about rule 2: trust needs boundaries.

I like this one - set clear boundaries for expected results, expected performance, then let people get on with it. Trust them enough to believe that they will perform within your boundaries. I think this is really important for creative work like design, problem solving, product innovation. Freedom within boundaries, particularly for self-contained work, lets people have some control over the way they work. If I see you trusting me, heck, I might even trust you... a bit... ok more than before....

I think my favourite is rule 7: trust requires leaders.

The article I referenced above suggests that many leaders are required - at different times and different levels - for a group or organization to be successful at achieving a goal. The author suggests that it is not possible for "... all the leadership requirements [to] be discharged by one person, no matter how great or how good." I want my leaders to be around when needed, to get out of the way when not needed, but to also help keep all of us accountable to each other and the organization. I trust my peers and cohorts when I know they are also being led, that the team is aligned and working towards the same goal, even if we contribute in different ways. 

What stuck with me is that it's for all of us to play the role of leader sometimes. It can't just be one person. But this only works if we all have the same shared vision. Oh, and remember that we are entrusted to take good care of it.

Day 440: What does it mean to be an expert?

Expert
def. someone widely recognized as a reliable source of technique or skill whose faculty for judging or deciding rightly, justly, or wisely is accorded authority and status by peers or the public in a specific well-distinguished domain (Wikipedia).

Many people I have spoken with about my Master Black Belt program have said or asked something along the lines of "so you're the expert then?" And most times, I say "nah, I'm still learning, still have my training wheels on." But with only a few more months left in this program, I had to start having a conversation with myself about being the expert.

So, let's say you have decided that today is the day that you are now a real expert(tm) at something. Yo-yo tricks. Dog whispering. Cardiac bypass surgery. Lean management. Whatever it may be. You might even get it put on a business card. Maybe a t-shirt. Bumper sticker? Cool.

So I have a few questions for you, if that's ok? Humour me.
1: What makes you an expert? How did you know?
Expertise is often externally validated, such as a designation or certification, but sometimes it's about the experience under the belt (no pun intended - I think?). Experience in making good decisions or maybe experience in performing a specific task. Similar to mastery, but I think, more focused. More specific. 

I started coaching U12 flag football this spring, along with 4 other coaches. Practices have a structure, similar to those in other sports: warm-up; skills and drills; practice/play; cool-down. While I am no expert in the game, I have a sufficient level of skill and knowledge to contribute to most of the parts of the practice. However, where I was able to add a LOT more value to the group was in the warm-up and skills and drills - apparently over 20 years of athletics in a wide variety of sports (and dealing with all those sports injuries I suppose) has given me a level of expertise in how to move. Do a lunge like this, not that, and here's why. Load your legs for a sprint start like this, not that, and here's why. 

2: What changes now? I assume that you still put your pants on the same way - one leg at a time - so some cool expert pants-putting-on contraption or skill aside, what changes now that you are deemed an expert?

I guess that what changes is... me. I don't know if I would ever consider myself an expert at anything as there is always something more to learn, some additional skill or aptitude to further develop. But that doesn't mean that I don't have more education or experience than some. In the grand scheme of things, I'm still somewhere on the big bell curve of learning - sometimes on the leading edge, sometimes on the tailing one.

Simply put, being deemed an expert is a contextual designation. It depends who you are being compared against. Compared to my 11 year old daughter, I am a math expert. Compared to my 4th year math prof at uni, I am at a child's level of mathematics. So what changes? I guess I get measured differently - it's a different metric now.

3: Will you use your powers for good or evil? Since you have a choice here, are you going to help others by providing your expertise or are you going to hoard it all, meting it out only when it suits you?
Only for evil. Just kidding. :-)

AMac

Day 404: Penny Wise, Pound Foolish

OK, we've all been there. Some great idea to improve a process - shorten cycle times, reduce defects, improve customer value - gets everyone excited, energized, ready to help make it happen. 

We value streamed this, and we SMED'd that, and along the way, we laughed, we cried, but we persevered and behold, an improved process was born!

Then it turns into "how much money did you save?" and folks kinda shuffle their feet, look out the window, scratch their heads and try to explain... "ummm... errr..."


I love saving cash. Money money money. I love when the company makes more profit, money money money. It lets the company grow, develop better products, expand their market reach, invest in their people - all great stuff.

But sometimes, it's not about the money. Sometimes it is about the journey, the learnings, about the improved working conditions or employee morale (to which you could attribute a cost savings, if you wish). Success comes in many shapes and sizes; we shouldn't assume it looks like a dollar bill.

Mind you, some times it is about the money. Usually, the money comes up when things aren't going so well, when suddenly there is less money than wanted. No one likes bringing up the subject of the money in this situation; it's the giant elephant in the room. It's easy to try to focus even more on the money when doing kaizen in these situations, but we have to be steadfast and continue on the path of improvement. If one improvement yields little to no direct cash, but has other benefits to the organization, that one improvement may end up being the start of a much bigger result - the foundation of future wide-scale changes - the kind with truly large financial impacts to organizations.

Rome was not built in a day, and so we should let each kaizen be seen as the small incremental steps we take each day towards building the empire we want.

AMac

Day 383: Committing to a goal - when to keep going and when to stop

This week, I am competing in the World Master's Winter Games in beautiful Quebec City. I love visiting Quebec, even in winter, when it can be bitterly cold. I had been training all season for this week, and would compete in long track speed skating, short track speed skating, and for my first time ever, attempt a 50km skate marathon.

I had very good success at the long track and short track events, with many new personal best times and a lot of medals. But along came the marathon. 

In reality, I had no idea what this would be like. 30 laps on a 1.65k track on a lake, with cracks and bumps and uneven surfaces. It was blindingly sunny, and cold enough to be a concern (-15 degrees C with a steady ~15kph wind). But I was here and it was there and so I figured "how bad can it be?"

Anyone who knows me knows I am pretty stubborn. I hate not finishing what I start. I know that if I believe I can finish, I do, that mental toughness is what gets me to the finish line. But 2/3rds of the way through this marathon, I was beginning to think that perhaps I had met my match.

Starting lap 21, I realized that my left hand was starting to go numb. I had packed in my jacket pocket some fleece hand covers (think: basic mittens) for exactly this situation. I pulled one on and within a lap, the hand felt better. Then the right one - same problem, so same solution, right? Well, I guess that left hand hadn't really warmed up because it probably took 2 laps to get the fleece cover on my right hand. I had to use my teeth to pull the cover on, and to position it. At one point, I accidentally bit my right hand - and couldn't feel it - at all.

That's not good, I thought to myself, really not good.

6 laps to go. What do I do now? Finish? Quit? I had already committed so much time and effort, and was so close to being done. But I knew this was getting very close to the edge of being dangerous (frostbite perhaps? Nerve damage? Hypothermia?) so I better decide. Ok, I'll decide at the end of this lap. 

Which turned into the next lap.

Then the next lap.

Two to go. I can finish. I tried to wiggle my toes, something I had been doing every half lap (every turn), and realized they were now numb too. Oh MacIntosh, what have you got yourself into this time?

I put my hands in my armpits and kept skating. In all honesty, I don't think I would have been able to stop skating unless I fell or finished, whichever came first, my legs just kept going and my brain was no longer playing the "go or stop" game. At the far end of the track was a volunteer, who had been out there cheering us all on the entire time and spotted my armpit hugging stance. He stepped out as I made the last turn of the race, and gave me his huge, wonderful, warm mittens. 

The last stretch was probably my fastest leg of the entire race. I crossed the finish line and immediately bolted for the warming hut and the hot chocolate. I sat in the hut, wearing all my clothes, shivering for at least half an hour, and even today, the day after, I still have some tingling in my big toes and one fingertip.

Why didn't I stop? I clearly knew I could have seriously hurt myself. There was no pride in stopping, in not finishing, as many others had already done so throughout the race. And this was my first time trying, right?

It comes down to self-persuasion. In Robert Cialdini's landmark book Influence: The Psychology of Persuasion he described the six universal principles of persuasion: reciprocity, authority, scarcity, consistency, liking, and social proof. I wanted to be consistent with my commitment to finish, and with my already-committed efforts so far (if I didn't want to finish, why had I already invested 20+ laps into this endeavour?). I wanted to be part of the social proof where others had already finished, and I wanted to be in that group (if they can do it, so can I right?). The scarcity, or exclusiveness, of the finishing group was also appealing (this is pretty bad ass, not a lot of people can say they've done one of these). These factors essentially got me to the finish line, even when there were clear signs of risk to my well being.

It is amazing what we can persuade ourselves to do.

AMac

Day 355: When a Standard isn't the Standard

Yesterday, I wrapped up a three day Whitebelt training and kaizen session, focused on our field services group, at our Toronto office. The group was an interesting mix of field technicians, project managers, service engineers, and most of the participants had to travel from their home or regional offices/work sites for this session. This group rarely got together on the phone let alone in the same room. 

They were a lively bunch, with a strong "git 'er done" attitude. After learning about value, waste, flow, 5S, fishbone/root cause analyses, RACI matrices, value stream mapping and value graphs, they went off on their way, looking for the gold, the opportunities to help improve their work and ultimately the outcomes for their customers.

Three days of searching, stumbling, spinning wheels, gaining traction, and moving forward, they reported out their findings. Lots of low hanging fruit, some really clever ideas, and some contentious ones. Contentious?  Whaaaa?

Yes - contentious because their investigations revealed that a previously developed standard was not being followed. Senior management had made it very clear that the standard was to be adhered to, yet reality showed that it rarely was.

So what happened? Why did the previous standard fail? People generally want to do a good job, so when they don't do some task a certain way, or use a certain tool it's because they either a: don't know how to do the task/how to use the tool, or b: they don't want to do so. This was a case of the latter - no one did the task, followed the standard, because it was perceived to be a big fat case of over-processing. They all wanted to do the right thing, but they also couldn't reconcile the process standard as prescribed with what was best for the company and ultimately the customer.

I can only imagine how utterly frustrating it must have been for the process owner (on the other end of a video conference, 5000kms away to boot) to hear this. To have spent the time and effort to put the standard in place -- with all best intentions -- only to hear that despite repeated directives to follow, that he was essentially walking alone.

What was surprising, however, was the perceived (over the phone, remember) steadfastness to the existing standard. I have always had external standards to which my organization had to adhere - ISO 9001, 14001, IEEE, etc. and with those, your challenge is to meet its requirements with as little effort or onus to your organization. However, internal standards are our own doing - so it's up to us as to when they should be revisited, improved, or removed even. 

We often talk about "the gap" when defining a problem. The gap is the difference between the current state and the desired, near-term future state. We use our tools to investigate this gap and to develop ways to close that gap. So given this current state, this gap between desired behaviour and actual behaviour, how do we close the gap?

Well, I guess we negotiate. 

Yep that's right, a good ole fashioned back and forth. Quid quo pro, as it were. Each side must be willing to give up a little to come to a common agreement, a common outcome. There has to be a middle ground here. Or even progress in the right direction. Anything would be better than this situation.

There are always real deal-breakers in any negotiation, those key points that cannot be relinquished or positions that cannot be softened, but there is often quite a lot of wiggle room. There is always room for improvement right? In contracts, we look at the intent of a clause, not just the letter. So it might be worth looking at the intent of this contentious standard. What problem was it trying to solve when it was created? Is that problem actually still a problem? Or have things changed enough to justify a fresh look at the situation and this standard?

Considering what I heard during the report out, I'd say it's worth the effort to do just that.

AMac