Sometimes we need to reframe our problems to devise better solutions, for instance when we're overloaded with work and need to take on new interests or responsibilities. I've found one useful technique is to use a 'power of 10' to help reassess my current approach. Here are some examples of how it works for me:

I imagine I'm now responsible for ten times the amount of work, with my current work limited to one tenth of my commitments, which allows me a maximum of 1/2 day per week for it. What are the most useful and important things I can do with my time to help and support my current project? Then I try to make sure that, from now on I do that work first each week. Of the remaining work, inherently it's less important so I try to pick the next most important tasks and do them next, etc. Eventually, say after 2 days per week I decide the rest of my old work is no longer useful so I don't do it. Now I have 3 days to take on new work, learn new skills, fix problems, etc.

Another use of powers of 10 is to imagine I have 10x the number of testers, machines, etc. - how would I use them to improve my testing? Generally I find I have a list of possible ideas with some idea of how much they'd help. Now I pick a few of these and implement them (possibly in the time I've freed up from the first example :)

Note: try using powers of 5 (to match one per day of the working week), 100 (e.g. test machines), etc. to help breakthrough your current mindset and challenges.

I do a lot of writing, and sometimes I get blocked. I sit there staring at the page, and nothing comes out. The same thing happens sometimes when I'm testing. Sometimes it helps to figure out why I'm blocked:

• Have I defined the problem correctly (or as completely as I need to)?


• Am I using the wrong approach?


• Am I using the wrong tools


• Do I have incorrect data?


• Am I unable to fully engage because I'm tired, frustrated, or bored?

If I can figure out why I'm blocked, often I can take the appropriate action to fix it. I can redefine the problem, change my approach, change my tools or data, or just step away for a bit if that's what I need.

Sorry, I wasn't trying to be mysterious about my notations.

The short answer: I use the letter "T" next to ideas. I know my notes well enough (in terms of my own writing style) to be able to scan a notebook and find those ideas.

The point about notations is much like managing a calendar, it doesn't matter where or how you keep it but that you keep it predictably and stick with one format.

Here's a link to my blog with a long list of what and how I keep notes:  http://www.testingreflections.com/node/view/6536

When running load runner tests, I grab screen shots of the settings used on the Controller. Its a fast way to keep track of the settings. And if an arguement comes along after testing about what settings were used, I have proof. Settings in the Controller are essential factors. I would imagine this same tip could be applied to other tools.

Most defect management tools are configurable to send you an email when events occur on tickets in your queue. Sometimes, this can get annoying, and many times people I work with direct those messages to a folder and never look at them. Instead, try using an RSS feed from the tool. Example tools that supply RSS include JIRA, Bugzilla, and FogBugz.