Micro Blogging - Twitter Updates

    follow me on Twitter

    Wednesday, November 30, 2011

    Do learn. Do not follow.

    I can't insist enough in the importance of original marketing strategies: study and learn from your competition, yes, but don't copy "now".

    Specially do not change your strategy because you liked the new campaign (no matter how good it can seems to be) from competitor X or Y. Keep the good idea in your backlog for the right moment. If not, you will simply be a follower.

    Tuesday, November 15, 2011

    On Tools and Skills

    Tools

    Change is the path for improvement. Adaptation is what made us what we are. 

    Too often the first step to implement change is the adoption of a tool. However tools are just tools and if you are lacking skills or purpose understanding, change won't happen. 

    Tools allow for speed increase, and simplification (or automation) of a task. But tools will never bring you the skills. You will never become a better project manager by purchasing a project management tool. Your finances will not be managed  better by the implementation of an ERP system. You need to understand the concepts first, master what you have to do, and then use the tools to increase performance. If you are working with a team, the team needs to acquire the knowledge and understand the motivation too.

    If the knowledge and the skills are not there, you will only face resistance and rejection. Make sure you have the mindset and skills before considering any tool adoption.

    Thursday, November 10, 2011

    How to determine your next action:

    You've got your "To do" list with all the projects and tasks you have at hand. 
    For projects you have carefully prepared, the choice is often easy. it is easy because you have, at least in your mind, the order of events or tasks you need to perform to get your project done.

    But sometimes, specially when overwhelmed, the next action is not appearing naturally. 

    In order to solve this, trying to assess the possible risks could be a very good option to determine the first task you need to do, and the second one and the third etc...

    An option for this is to use an excel sheet, where you will list the tasks you need to perform. Aside the task, the level of risk, and the risk approach you want to take for this task or action will be set: Accept the risk, Mitigate the risk, Avoid the risk. 
    You can of course make the sheet as complicated as you like. I also normally include the project name, the project phase, a type of risk if necessary, and all sets of data that could be crucial. 

    As an illustration you can check this simple risk management sheet, where I left a couple of examples:
    Risk_assessment_made_easy

    In these examples, I would first perform the actions triggered by the "High" level of risk level plus the risk management approach set to "Avoid". 

    (For Project065233 first I will make sure I have a vendor for the language I'm missing one, then I'll make sure to ask DTP engineers to correctly setup the file to avoid multiple corrections when getting the translations back. Then I will move to Project065231 and call the client to make sure they understand the consequences of having multiple small batches being worked on before having the content closed).

    Feel free to use it and customize it for your particular needs!