Update: Sep 5, 2022

Image credit: Andrew Neel. Source: https://unsplash.com/photos/cckf4TsHAuw

It has been a few months since I started working on this website and blog. I have expressed that this is my place to celebrate myself, share stories, showcase my experience, and discuss topics of interest.

Already I have suffered a hit: I have gone two months without any updates or posts.

But why?

What happened?

I scored a contract! (Yay 🥳)This was my first one running with my own practice; it was interesting, and I was eager to start.

Where did I struggle?

On the contract side, I suffered consequences I wanted to avoid when I started this practice. The biggest one: this project consumed me. 

I quickly fell into old habits of working long hours, working at a rushed pace, dropping my activities, and missing social engagements to make it work. I worked on a tight deadline for a demanding client, and the scope changed constantly.

What did I learn?

As my first project, I took the contract at a loss. It appeared straightforward, and I took it mainly to build momentum and get experience running the entire thing myself. Usually, I have dedicated resources to do this. My boss provided the assignments when I was employed, and HR handled my salary. When I was a consultant, the partner got the contracts, the account managers handled the paperwork and fee collection, and HR handled my payments.

Several events happened that I should know better as a ten-year veteran in the field. But being solo without a dedicated support system changes everything. You really appreciate having a team working with you.

Here are the lessons I intend to incorporate for the next project:

  • Always dedicate at least two weeks for an evaluation before signing off on the scope. This is the time to test the proposed scope, build a few prototypes, ask as many questions as possible, and create a reasonable estimate for the project.

  • Each project is unique and should be treated with special care. This is not the same as building a house; there is no cookie-cutter solution to solve problems. Each project, and client, bring their own variation to the problem that needs to be addressed.

  • Make sure the scope is clear, ironclad, and signed. This is very important to avoid scope creep and other challenges that arise during a project.

  • Scope changes happen. When it does assess the impact and negotiate the timeline and fees appropriately. Document everything, and get it signed.

  • If there is a Project Manager involved, put them to work! Use them to help chase down the client or other resources, and stay focused on the task.

  • I favor throughput over responsiveness. This means that I need to be clear with PM (or client) that there are set windows that I will be available for interruptions, how to reach me, and when to expect my response. Anything outside of these better be urgent.

  • Clear and concise communication. This is my preferred style when working on projects. Some cultures demand this. Others have a more relaxed and casual style. It is essential to recognize this and adjust, but I default to being factual and getting to the point. If an email trail starts getting out of hand, have a meeting instead.

  • I’m not a body shop; I am a problem solver. I do not like busy work; I do not do things for the sake of it. I like my Research & Development-oriented work incorporating design and engineering into the solution. The solution must not just be robust; it must be simple and pleasant to use.

  • Maintain balance between client work activities, my work activities, my social and networking activities, and my fun activities. They are all significant to me!

Why am I sharing this?

I intend to be clear and transparent about my practice and the solutions I deliver. This is important to me. There are no “black box” solutions, and there are no mysteries with what I am doing. I prefer not to be called with issues of a past project, and so far no one has. I prefer that if I get a call back, it is because they like working with me and there is a new problem to solve. This journal-style entry is a part of the clarity and transparency. Maybe you, the reader, will also learn from it or, even better, share suggestions!

What’s next?

Take a short break, create more content, learn new skills, continue networking, build the things that need building (I have many things!), and find the next contract. It only gets better from here! 💪

Murali

Murali is a data scientist with over ten years of experience in many industries including Banking & Finance, Insurance, Technology, Operations, Logistics, Retail, Marketing, Telecommunications, and more. He specializes in transforming teams into data-driven cultures that drive fact-based decisions. He is very passionate about data & analytics believing that by empowering people with modern tools and data literacy, everyone can become a powerful analyst and thrive in the face of any challenge.

As an engineer, he uses his critical thinking ability and growth mindset to drive for a better tomorrow. This is the foundation that drives him to produce innovative and creative solutions for complex problems, using design techniques that keep people at the forefront of the solution.

Outside of the working world, Murali enjoys many hobbies such as scuba diving, free-diving, coral restoration, surfing, hiking, photography, chess, dog training, dancing, and more!

Previous
Previous

Tableau Conference 2024

Next
Next

Sometimes the worst advice is the best advice!