My partner and I decided to buy a house recently. We had the dilemma of which suburb to commit to living in for the foreseeable future (be gone the days of renting). What caused this problem for us is that we both grew up in different parts of the city. I was a Northsider and him a Western suburbs guy. Had he been a Southsider, the relationship would have been doomed – in my town you just don’t cross the bridge.
We both recommended what we knew. From my point of view, Northside is where I was born, where my parents live, where my siblings have settled down and where my friends and their families had done the same. I would never consider the Southside and only partially be open to the Western corridor (I guess it was love as it definitely wasn’t road works on the freeway!). Southside was soooo far away. Southside needed a freeway to get anywhere (it’s a Northsider thing). But this predicament forced me to stop and reflect on my reasons for dismissing the Southside (our idea of comprise was neither of us got our “way” so that left South as East was too expensive). It forced me to go back over what I knew to discover maybe there’s more to it.
There’s more than one way
Being open to learning new ways of working is necessary for a successful career. Life changes and so does SAP. In my current job, I am wearing the customer hat in a type of Quality Control role. It is a very strange situation to be in where I am not the architect (my boss jokingly told me not to void the contract by taking over). But what is has meant is I am working with Architects who have different approaches and ideas on how SAP should be implemented. And this is where I have again found myself in a situation where I was unwilling to consider some options as I had never done it that way. I won’t go into the specifics (breaking client confidentiality and the ability to bore you aren’t my goals here). But we found ourselves debating which is best.
Re-learn what you know
In preparation for my role as the customer representative, I wanted to make sure I was in a position to identify any gaps in the solution, build and also ensure the solution was supportable (projects get you to go live but someone has to keep the lights on afterwards). The solution was using new technologies but also the latest Basis release – 7.40 (and running on a HANA platform so my inner techy nerd was on cloud 9).
In addition to up-skilling on new technologies and platform, I took this as an opportunity to revisit my current knowledge. My motivation in doing this is to eventually sit certification (it’s on the list) but also SAP has changed so much. I have been working in SAP security for 10 years now but a lot of the fundamentals I know were taught to me at the beginning. On a 4.6 system.
Part of this realisation, is some of what I know may not be entirely accurate. Some of justifications for certain build and design approaches may no longer be valid (perhaps there was a system limitation back then or performance issue). Some of why I processed requests were based on who taught me and they didn’t know any better. Some more may have been due to different client exposure (different industry, customer base, components in scope and other complexities).
By forcing myself to revisit the information (this week involved stepping though standard SAP help Security Guides and re-reading everything I usually disregard as I already know it) I discovered what had changed. I could see where SAP had made progress and improvement which were more than likely to resolve the original limitation. I discovered new tools. It has meant technical approaches once deemed unworkable might now be useful. It has also meant new ways to support security and audit, and these can be incorporated in the design to ensure a better outcome for my customer.
Be open to changing your position
Keeping yourself current with the technologies and options is the first step. But the reality is, if you are only prepared to work one way then you will find yourself moving from client to client with a cookie-cutter approach to design that is at risk of becoming outdated.
In collaborating with these architects it created situations where we got into debates on different technical approaches. What was fantastic about this discussion is both sides discussed the positives and negatives of why we should design the solution in such as way. We all looked at it from different points of views. And in the end, we both adjusted our view points and incorporate the best approach for our situation. It worked well as we respected each other opinions and were all prepared to adopt the others position so long as it was justified. In one situations, my straight out feedback was “I really don’t like using XYZ but if you can explain and justify why then I’ll support your recommendation”.
In preparing for these sessions, I had re-taught myself. In participating in these sessions, they taught me.
My challenge to you for 2015 is to teach yourself something you already know. Choose a specific SAP topic that you think you know inside-out or a rule or principles that you have applied as “that’s how it must be done”. Take those assumptions and push them to the side. Have an open mind.
In this challenge, retrain yourself and see if you can discover alternative options. Read up on SAP help. Join the SAP Learning Hub (even the free edition). Discuss ideas with your colleagues and peers. Search your SCN space (maybe even create a discussion if it’s not a basic question). Go in with an open mind. Learn.
And you never know, you might just have taught yourself something yourself thought your already knew 😉
Oh and forgot to mention – been living happily on the Southside for the past 6 months. Northside is now sooo far away. Southside is so close to the city and airport (work home is on the side of the country), has fantastic restaurants, close to the Gabba (cricket fans can pick the city) and just love my home, its location and my neighbours. Turns out, the freeway isn’t that bad after all!