July 25, 2017 

© Copyright 2018 MBO Partners

A blog is more than something to update with your weekly experiences as an independent professional—it’s an opportunity to engage and grow your target audience. Blogging is a great way to showcase your expertise, bring in potential clients, and grow your personal brand. In fact, 53% of marketers say blog content creation is their top inbound marketing priority.
Blogs are simple to create and maintain, and can help you market your business while building your brand and audience. Here are four reasons to consider making a blog a part of your professional website.

1. Engage Your Target Audience
​A successful blog engages readers. There’s something about a blog that is simply more believable and personal than reading a company fact sheet. Blogs are a chance for you to share your voice, and show that you know what you’re talking about as a professional in your industry. While some blogs may turn off readers by acting solely as an opinion column, if you back your statements with research and proven facts, you can build trust in your readers.
Potential clients are looking for an independent professional who is knowledgeable. They want to be sure that you’re really an expert before engaging your services. Providing readers not only with information about how you can help them solve their problems, but also with industry advice and updates, will show them you’re someone who cares about your business as well as your clients.

2. Build Brand Awareness
Blogs help build brand awareness, particularly by increasing traffic to your professional website and improving your visibility on search engines like Google. By consistently publishing new content that includes keywords and topics your audience is interested in, your website will appear more frequently in search engines results. Be sure to share any new content you write on your social networks to drive traffic as well.

3. Future Clients
Your blog is an opportunity to provide your target audience with the voice and personality behind the services you offer. By discussing industry news and trends and backing up your opinions with research, you can begin to establish yourself as a go-to authority. When searching for content ideas, think about common questions your clients have, and create helpful posts around these topics. This will help build confidence in your audience, and ensure you are top of mind when they are in need of expertise for a project.

4. Build Strong Relationships
A blog is an ideal place to build strong relationships with existing and future clients. Engage your readers by asking them questions in your posts. Then, encouraging conversation through comments and feedback. Developing a positive rapport with your readers is a great way to develop trust, and it can also help you gain insight into additional questions potential clients have, what they may be looking for in your services, and what types of problems they are dealing with. 
The best part about creating and maintaining a blog is that it will continue to produce positive effects for your business in the long-run. So long as you continue to produce quality content, old posts will still be relevant to your audience well into the future. 

(We can consider many Frameworks or Methodologies like Agile, PMI, Lean, etc.)

A Developer is suffering with all the pressure of the Universe to have this solution up and running in production within a very short time frame, let's say a week, give or take. Since he knows better, like many developers, he does not need to conceive, design, validate, proof or test the concept or the feasibility of the solution.

Then the developer creates the world in six days, all by himself. Guess what, he runs out of resources or ideas to continue this lone and selfish journey. During a bio-break, he has yet another brilliant idea: he is going to use his own poop to be able to continue. So he grabs as much turd as his hand can take and uses it to fabricate the resource he needs: a man.

Immediately the developer finds out his implementation is flawed, besides being already late and out of resources. The first feedback man gives to the developer is that he needs help, he needs companionship to be able to continue the developer's work. The developer has one out of two options: either he asks help for a weird speaking sneak that is coiled around a tree nearby or try to use whatever the result of his molding turd was.

Well, lacking a better idea and regretting big time for not validating with future users and clients before, he radicalizes and decides to remove a piece of the code from man, and with the rib shaped function he creates the next resource. However, besides having changed radically the code without proper validation, change management and approval, he creates the next resource.

No surprise it was not another man. Both developer and man agreed to use the name woman for this new resource.

Time goes by ...

The system proves to be crap. Nothing works. Man and woman were able to multiply their codes like a fast spreading virus. Developer was helpless and severely criticized everywhere. His only option was unilaterally purge current deployed system and erase it so that a new, better solution could be deployed. This time he decided to work smarter. He asked a group of people to help him. He came to realize it was the family of an old, blind, drunk dude with great skills, just what he needed.

This dude built a gargantuan ship with his bare hands, something never did before, and that will never be replicated in the entire cosmos. Soon the developer purged the entire system, flooding the host machine so that all his mistakes could be erased forever from memory. The family of the dude was responsible to make it all run again. After one year he gave a few coach class tickets to Kangaroos to go live in Australia and the different Penguin families to live in Antarctica.

Developer tells there was a time of productivity and efficiency. Few people believe him. Until all the system went down south once more. The situation was worse than before. The code was full of bugs, many OS vulnerabilities were explored by scammers and other hackers with bad intention.

At the end the developer was totally screwed ... again.

He became depressed, restless, ashamed for being so selfish and arrogant for believing he was all powerful and had all knowledge in the universe. He found no solution, he need to offer himself to sacrifice. The only way to clean up all the shit he did during millennia as a mediocre designer and even worse developer.

So he did. He manipulated the code so that people would think he was someone else and offer himself to sacrifice, and users were happy to do so since they knew this under-performer, unskilled and mediocre developer couldn't ever do any better.

Today we have many great tools, including MSF (I love it still), Agile (Xtrene, Scrum, etc), PMP. PMI. ITIL, ITSM, DevOps none of us has to live through the shame of incompetence and very poor design.

I do not give exceptions: design thinking for conception, Lean or MSF for implementation, ITIL for operations.

To rely on crap when you run of resources is a big sign your product will be the end of the world,

PH - Hune/21/2018  HAPPY SOLSTICE