One of the most exciting things about being an analyst in ThinkWorks is to be in very different business fields. In one project, you may be in an investment bank, sitting in a room next to the merchant floor; Or, you can study the differences between 5 different designs in providing a retail commercial exhibition, and you are within two ears of fashion shooting.

Such differences in the physical work environment screaming indicate how to adapt your work methods. Adapting your ways in the sense that you need to adjust how to communicate and deliver your thoughts to your audience so that the message can be heard in the right way. The same thing elsewhere, itself to Rachel. The specified implementation method should be allocated with the specific needs, wherever you are.

Some of these alleged differences are clear, for example, the work environment or the physical space in which the project is located, while others are more accurate and captured by interaction. As analysts, we don’t only get to know the type of tools that help to facilitate people, but in the situations you will apply and how. By admitting these differences, this may help you to determine the best possible approach that you follow.

Below is a sample of things that helped me through various projects.

Adapting your tools

Picking requirements while flying from Day Zero is a large part of analysts. Just because you pick up the requirements, it should not be done in one solid way. At some point, you may do this on 4 X6 Index cards, it may be on Excel if you are faster to write, or maybe you are doing it to mix. Choose the best way for you and put. The important thing as an analyst is that the essence of the story and ideas behind the conversation is captured. You can do this quickly as long as you can remember such conversations or a high -level idea, as it allows you to return to the people who reached them for the first time and continue these conversations. This is the main goal of your actions.

For example, when you are in a compressed scenario of time such as story writing workshops, you cannot spend all your time in the afternoon in discussing a handful of stories only (if you do so, your upbringing will continue for several months, and you will lose all other value conversations that you might have might have instead). Break things with pen and paper, carry a luxurious moleskine so as not to lose drawing scraps (or notebook). What about the white plate and take pictures on your smartphones? Submit it on your iPad?

Adapting your methods

How to submit the requirements captured by the same importance as what you wrote.

In a previous project, customers were very visually present and did not respond well to the lists, documents or novels well. Or anything consisting of reams and reams of the text. In these circumstances, either you go ahead and do it anyway, which risk the loss of your customers with their interest in meeting, or you think about other communication methods that would capture your audience and transmit the same message well. This facilitated a priority workshop with pictures drawn on the cards. Sometimes I take the conversation points on a mental-simply painting tool because the visual tools speak higher for me and I would like to be able to present this to the customer.

Adapting your own interpretation to the local field

It is not literally the local language (although I did this), but adapt your vocabulary to the customer. Indulging in their world. Use their own domain language to break the connection barrier, and you will find that you will not fight a lot of battles based on trivial things such as “we call it repetition and call the enemy”, and instead focus on solving the problems of the real world.

Continuous improvement and continuous learning

Agile is not a specific set of methods that, once you use step -by -step, will solve all your problems. It defeats the name and defeats this point, really. The trick does not apply to any one to the point that you hinder yourself from discovering a different way to solve a problem. I have seen more dangerous practices / restrictions that were applied to projects or departments that, in the end, were damaged more than it is useful. Just because you are standing, you are not graceful (you still practice the waterfall methodology everywhere). It is not a sticker associated with practice. It is the basic principles of the continuous improvement that many ignore; It is known that you are not here to adhere or comply with the set of rules, but to constantly search for a better way to do things; You ask yourself this question constantly, knowing that you will definitely find these improvements that will exceed your previous ways and outperform them.

It is not a matter of reaching the smartest advanced system and allowing monkeys to run with it; It actually puts the smartest people you can find in any system and trust them that they will bring the smartest system for themselves.

About Jenny Wong

One of the most exciting things about being an analyst in ThinkWorks is to be in very different business fields. In one project, you may be in an investment bank, sitting in a room next to the merchant floor; Or, you can study the differences between 5 different designs in providing a retail commercial exhibition, and you are within two ears of fashion shooting.

Such differences in the physical work environment screaming indicate how to adapt your work methods. Adapting your ways in the sense that you need to adjust how to communicate and deliver your thoughts to your audience so that the message can be heard in the right way. The same thing elsewhere, itself to Rachel. The specified implementation method should be allocated with the specific needs, wherever you are.

Some of these alleged differences are clear, for example, the work environment or the physical space in which the project is located, while others are more accurate and captured by interaction. As analysts, we don’t only get to know the type of tools that help to facilitate people, but in the situations you will apply and how. By admitting these differences, this may help you to determine the best possible approach that you follow.

Below is a sample of things that helped me through various projects.

Adapting your tools

Picking requirements while flying from Day Zero is a large part of analysts. Just because you pick up the requirements, it should not be done in one solid way. At some point, you may do this on 4 X6 Index cards, it may be on Excel if you are faster to write, or maybe you are doing it to mix. Choose the best way for you and put. The important thing as an analyst is that the essence of the story and ideas behind the conversation is captured. You can do this quickly as long as you can remember such conversations or a high -level idea, as it allows you to return to the people who reached them for the first time and continue these conversations. This is the main goal of your actions.

For example, when you are in a compressed scenario of time such as story writing workshops, you cannot spend all your time in the afternoon in discussing a handful of stories only (if you do so, your upbringing will continue for several months, and you will lose all other value conversations that you might have might have instead). Break things with pen and paper, carry a luxurious moleskine so as not to lose drawing scraps (or notebook). What about the white plate and take pictures on your smartphones? Submit it on your iPad?

Adapting your methods

How to submit the requirements captured by the same importance as what you wrote.

In a previous project, customers were very visually present and did not respond well to the lists, documents or novels well. Or anything consisting of reams and reams of the text. In these circumstances, either you go ahead and do it anyway, which risk the loss of your customers with their interest in meeting, or you think about other communication methods that would capture your audience and transmit the same message well. This facilitated a priority workshop with pictures drawn on the cards. Sometimes I take the conversation points on a mental-simply painting tool because the visual tools speak higher for me and I would like to be able to present this to the customer.

Adapting your own interpretation to the local field

It is not literally the local language (although I did this), but adapt your vocabulary to the customer. Indulging in their world. Use their own domain language to break the connection barrier, and you will find that you will not fight a lot of battles based on trivial things such as “we call it repetition and call the enemy”, and instead focus on solving the problems of the real world.

Continuous improvement and continuous learning

Agile is not a specific set of methods that, once you use step -by -step, will solve all your problems. It defeats the name and defeats this point, really. The trick does not apply to any one to the point that you hinder yourself from discovering a different way to solve a problem. I have seen more dangerous practices / restrictions that were applied to projects or departments that, in the end, were damaged more than it is useful. Just because you are standing, you are not graceful (you still practice the waterfall methodology everywhere). It is not a sticker associated with practice. It is the basic principles of the continuous improvement that many ignore; It is known that you are not here to adhere or comply with the set of rules, but to constantly search for a better way to do things; You ask yourself this question constantly, knowing that you will definitely find these improvements that will exceed your previous ways and outperform them.

It is not a matter of reaching the smartest advanced system and allowing monkeys to run with it; It actually puts the smartest people you can find in any system and trust them that they will bring the smartest system for themselves.

About Jenny Wong