Project Consulting

in CAQDAS Packages

Project Consulting in CAQDAS Packages

Our involvement in team and funded research projects varies greatly from project to project. For some projects we serve only as outside consultants. This typically involves participating in the initial design of the data analysis and the consequent set up of the project in the chosen software, initial training of team members in the needed software skills, and then continuing on an as needed basis to provide guidance and advice at turning points of the data analysis, and provide additional software training and coaching on an as-needed basis.

For other projects we are more involved as a team member, participating in or leading the data analysis, and training and coaching the researchers in whatever features of the program they need to use. With some projects we undertake the entire data analysis ourselves, and participate in the writing of the resulting papers. We have been involved in a range of projects, from evaluations to grounded theory studies, including studies in  family medicine, public health, education, and leadership and management studies.

Using CAQDAS packages for collaborative data analysis

Using CAQDAS packages for collaborative data analysis is rewarding if the procedures are well-designed, but problematic if approached in the same manner as lone research. We are experienced in consulting to collaborative analysis projects, having served as project managers or principal data analysts in many regional, national, and international qualitative and evaluation studies in diverse areas of the human sciences. Details and references are available on request.

Testimonials

Nick Woolf is the best instructor I have had for learning a software application....Nick's highly interactive teaching style significantly increased my success...I returned to work with renewed insight and ideas about where my research was leading. Nick presented a remarkably effective class for both new and experienced researchers.
Mary F. Annese, MPA, Research Specialist
The Casey Family Program

Blog

Calling for a revolution – we have to get rid of codes

Calling for a revolution – we have to get rid of codes
By Nicholas Woolf on Jan 17, 2019 at 06:17 PM in CAQDAS commentary

Codes are the example par excellence for our constant banging on about strategies and tactics. Reminder: strategies are what you plan to do, and tactics are how you plan to do it. When using a CAQDAS program, the tactics are very different in nature from the analytic strategies. A strategy might be to compare the men and women respondents in a study by separately conceptualizing the male responses from the female responses. The tactic to fulfil it will depend on the CAQDAS package you use, but it will involve software tools that allow you to collect together selected items of data that have been tagged or grouped by you in the software so that you can compare them on screen or in printed form. Whatever the tools in your chosen software, they will have nothing to do with the subtleties of male and female characteristics or gender issues. Instead they will involve processing data in the software to accomplish your purpose. These are two extremely different ways of thinking, but because both are called ‘coding’ you unconsciously and unhelpfully think about them in the same way. For this reason we should stop using the term ‘code’ for the strategies level of our conceptualization work.

Read more...

Mindsets matter: think about how you think about CAQDAS programs

Mindsets matter: think about how you think about CAQDAS programs
By Christina Silver on Oct 31, 2018 at 02:06 PM in Five-Level QDA issues & ideas

On 17th October 2018 I had the privilege of opening the Digital Tools day at the World Conference on Qualitative Research (#WCQR2018) in Lisbon, Portugal. My talk was called “Mindsets for harnessing digital tools in qualitative and mixed-methods analysis: The Five-Level QDA method”. My main message was that we need to be more explicit about the way we think about the role of digital tools in the research process and our engagement with them.

Read more...

Can tactics inform strategies?

Can tactics inform strategies?
By Christina Silver on May 25, 2018 at 08:41 AM in Five-Level QDA in practice

Analytic strategies come before software tactics: that’s the Five-Level QDA approach. But there are times when software tactics can usefully inform analytic strategies. This leads to serendipitous exploration, and fits well with the emergent spirit of qualitative research.

When analytic strategies drive software tactics the use of the software is meaningful – focused on the needs of the research rather than the capabilities of the program. But many CAQDAS advocates say that new software features (tactics) do offer new analytic possibilities (strategies), and so the relationship goes both ways. I agree.

While I usually discuss the downsides of software tactics driving analytic strategies, here is an example from the workshop I led at the MQIC in Berlin earlier this year of tactics appropriately informing strategies.

Read more...

A CAQDAS horror story: when tactics drive strategies

A CAQDAS horror story: when tactics drive strategies
By Christina Silver on Mar 22, 2018 at 06:52 PM

A key principle of the 5LQDA method is that analytic strategies drive software tactics. This ensures that software use is always focused on the objectives of the study and is appropriate to the particular methodological context.

But what happens when software tactics drive analytic strategies? Here is the most extreme example I’ve observed. In my next post I’ll discuss when software tactics can usefully inform analytic strategies without actually driving the process.

Read more...

How many codes are needed in a qualitative analysis?

How many codes are needed in a qualitative analysis?
By Christina Silver on Feb 22, 2018 at 08:53 AM in CAQDAS commentary

There is no answer to this perennial question - not even any guidelines. You need as many codes as you need - in other words, however many are needed to capture what's going on in the data in relation to your analytic focus and research objectives. How many depends on what you're using the codes to represent, how you derive them, and how you intend to use them in the analysis. I've done substantial projects with as few as 22 codes, and others that required several hundred.

Read more...