Tension 4 - Technical Approaches vs Creating Conditions for Change
Updated: Sep 15, 2022
Originally published on equitableeval.org on July 14, 2020
In my last post, I wrote about Tension 3 – Individuals vs Organizations vs Systems as part of a series of five tensions that I/we are struggling with as the Equitable Evaluation Initiative unfolds. In this post, I want to explore the tension between supporting the work of others vs creating the conditions for new mindsets, strategies and tools.
Tension 4: Technical Approaches vs. Creating Conditions for Change
When I first conceptualized this series, I realized I defaulted to the how too quickly. We know, and have all borne witness to, how swiftly the move to technocratic and tactical fixes can happen without fundamental changes in what, whom, and how we value. What’s the balance to strike and what and how should that be determined? And by whom?
We at EEI have taken a position that before we move to method (as an expression of methodology) we must stop, look around, and check our assumptions, know our history, understand deeply our context and bring our humanity and curiosity to evaluative work. Philanthropy more than any other sector is uniquely positioned to be different and do differently. The other actors in the ecosystem take their cues (and monies) and will adjust accordingly, for better or worse (e.g., Eyes Wide Open, Response to Strategic Philanthropy for a Complex World).
As the EEI team evolves through strategy execution and ever-changing context, the following can be said:
We are in the unknown driven by what we hold as core, hopeful about where we want to be, and comfortable with exploring multiple hows.
We deliberately reject the notion that as consultants we are experts (the most important ones) and have the answers. There is collective and different expertise needed to get to someplace new.
We seek partnership on multiple levels - individual, organizational and systemic. The innovation, prototyping and testing is happening in the field.
We know that we (EEI) are but a piece of the puzzle and that others have started this work and have said many of the same things we are saying.
We are temporary. We aspire not for perpetuity but obsolescence.
https://zimplercasinoplay.com was open in another tab while I read this, and it struck me that both casino odds and evaluation rubrics can look neutral while quietly deciding what counts as success. The call to stop and check assumptions before moving to method is the part I keep returning to, because I’ve seen teams default to tidy indicators when the real work was changing who had a say. It makes me think the slower work of creating conditions is what keeps technical choices from reproducing the same power dynamics.
Beauty services are often easier to choose by specialist rather than by salon name. Different studios may focus on hair, nails, skincare or specific techniques. A general search through Link.ua, followed by Odesa salons and Kyiv studios, can make comparison easier. Ternopil, Lutsk and Ivano-Frankivsk also have many smaller businesses with narrow specializations.
I found the general information about the p999 game useful because simple explanations are easier to follow. Knowing what the interface is like, what basic requirements may apply, and how account access generally works can help someone research the platform without unnecessary confusion.
Interesting discussion of the tension between technical approaches and creating conditions for meaningful change. The topic highlights an important distinction between simply producing tools and building environments where those tools can be useful. I appreciated the reflective tone and the invitation to think beyond easy solutions. Even https://www.goprogaragedoorrepair.com/ can serve as a small example of practical work meeting broader needs.
This is a thought-provoking perspective on why meaningful change requires more than technical solutions. I especially appreciate the emphasis on understanding context, questioning assumptions, and recognizing collective expertise before choosing a method. The same principle applies to Data Annotation, where quality outcomes depend not only on tools and processes but also on clear goals, context, and human judgment. A strong reminder that effective solutions should create lasting value rather than simply provide quick technical fixes.