Skip to main content

Pushing or pulling

 Corporate world requires you to think about strategies to achieve what you want.

There are mainly 2 strategies: push something forward and pull something(use the situation) forward.

In the first strategy, you are proactive. Maybe you have some leverage and you can use it. Maybe you have the authority to push a new policy and so on. Pushing when you are in a position of power is easy, and it is fast. There is no leadership in pushing. You just need to state what needs to be done and it shall be done.

Pulling, on the other hand, is an art. Art of waiting, a bit of chance involved as well. When you don’t have the authority, you need to leverage the situation. It is like a spaceship using the gravitation pull of planets to move forward. The challenge in this strategy is that your company or manager will never notice you for this opportunity, or the organization will never adopt the change.

Kodak was a successful company until it decided not to adopt the digital photography. Not that it didn’t do some attempts, but in reality, Kodak was always digital second.

Imagine you worked in the digital department and you see tons of potential. You might wait for senior managers to re-think the way the company is investing and prioritising, and you might have been right about it. But it never happened.

So this is the risk in pulling, unfortunately in the bigger percentage of time we all will be pulling and waiting for the right condition, technology and market disruption to arrive so we can benefit and jump on the train of success.

Comments

Popular posts from this blog

Where is the performance and load testing

I am reading the book “That will never work” by the founder of Netflix. From a technical point of view, something that really intrigues me is their launch process. The engineering team proposed an increase in server bandwidth to accommodate a higher request volume; however, the business unit expressed uncertainty regarding the projected demand. This result in a lot of guess work and a huge stress on the engineering team during the launch day. On the positive end, they did have stage and prod environment, which is a best practice approach. Scalable system architectures are now critical, yet comprehensive load and performance testing remains insufficiently prioritized. Similar things happened to Healthcare gov on it’s launch day. The key takeaway is the importance of proactive planning and scalable system architecture to accommodate fluctuating demand.

The last post

 This is the final post of 2023. I plan to take a break now. I wish you happy celebrations of 2024 and may next year bring us more joy and prosperity and focus on the most important things.

Perks of being part of a non-profit

When you join a non-profit, you do it because you believe in the cause. However, if you do something for free, you expect work and people you work with to motivate you to do your fully. If the culture is already toxic, don’t expect you will be able to change it. Then the perks of being part of non-profit are replaced with the pain of being in an organization that even doesn’t pay you. This is also the issue with political parties which want to attract people to promote their ideas. Most of the time, people see how bad the situation is and run away. Let this be the message for all the people who want to build something new based only on the idea. Give your followers or colleagues something they can embrace and enjoy to be able not only to at