Just what am I talking about now?
Well, let me explain; you see I am quite a techie when it comes to languages and architectures to solve issues, yet I am continually trying not to let myself get lost in the low level details unless I am working on a home brew project.
This is due to the fact, that while I do have a lot of experience of many kinds of architectures and solutions to technical issues be they data, systems or infrastructure focused. I need all of the teams I work with to own the architectures they use, and to do that I should only give simple direction on what can and should not potentially be done. By doing this I can ensure that not only do I not risk infringing any IP of companies I have worked at before. (as we know there is rarely anything completely new in architecture of systems and data management) But also that teams get ownership and develop the systems/architectures and solutions using their own skills and naturally develop a low level almost personal ownership of what they have helped create.
The above serves multiple goals the first being that I am not always referred to for answers on architecture and also stops me from getting lost in details rather than working on higher level issues that I am hired to deal with.
You could argue I suppose that I slow down development of new systems by doing this, to which I would counter with a statement along the lines of: “What would happen if for some unforeseen reason I am not available to answer questions on the architecture or provide a solution?”
As we are all aware having all architecture or solution design going through a single person is a very bad thing to do!
As a Final note, the getting to involved at a technical level is the bane of my life when working in management roles or assignments, whilst it is very good to have such a good low level understanding it is also too easy to get lost in it all and loose focus of ones real goals or indeed the companies goals that you are working towards.
No comments:
Post a Comment