Our Crisis
“Hindi nahi aati hai.” She doesn’t know Hindi. I stiffen. One of our first written pilot tests for the entrepreneurial assessment, and I heard this phrase. “Hahaha, Kuch nahi samajsukti hai!!” She doesn’t understand anything! I whip around to face Mandina and Aarti, and to my surprise, they’re not talking to me, an American working in India; they’re actually talking to each other, trying to address a question they can comprehend. f. Having spent months developing this tool as a Banyan Impact Fellow with ACCESS Development Services, this was our first written attempt at testing its questions and relevance. Yet here was our reality: Mandina struggling to comprehend the jargon, as Aarti read the questions over her shoulder, translating lofty phrases into something more relatable.

Photo Credit: Author
It reminded me of my own language journey, coming to India on a Critical Language Scholarship, where my first weeks of intensive Hindi study at the American Institute of Indian Studies were filled with formal grammar, traditional verbs, and textbook nouns. I quickly learned that many of these “correct” phrases rarely appear in everyday conversation. Returning to India this fall as a Fellow and again as a student with AIIS, thanks to the Banyan Impact Fellowship Professional Development Grant, I’ve seen how language opens doors and how formal study can fall short in the face of colloquial realities. That same gap was staring us down now. Our first digital pilot revealed that even native Hindi speakers struggled with our questionnaire, not because of translation, but because of how alien the formal vocabulary sounded. The wording we had chosen made our tool inaccessible, a lesson I knew too well from my own experience of learning, unlearning, and learning again.
Language is one of the key components to consider when designing inclusive tools. While we faced specific challenges with translation, these issues presented the far most difficult question. Comprehension. How do you ask questions in a way that they are understood? And at what stage of the research process does the specific wording of a question need to be taken into account? For my team at ACCESS Development Services, aiming to create tools for women operating micro-businesses in Delhi, the divergence of the colloquial language from the formal language created a critical issue in access and comprehension, revealing the larger issues of needing to consider participant comprehension at the center of tool design.
The Process
While building the enterprise assessment, we aimed to make a tool for women by women. Field visit discussions with groups of women entrepreneurs were followed by near-endless idea-generating and brainstorming sessions. Question by question, the team at ACCESS Development Services built our assessment tool. By the time we were ready to pilot, we had an entire Excel spreadsheet that automatically generated scored responses. Writing the tool in English, we didn’t consider language, because at this point, we thought we didn’t need to.

Photo courtesy of ACCESS Development services Shika Kumar
The initial test of the questionnaire was considered a “content-focused pilot” (Avnish). Manually rolling out the questionnaire with our field staff, our first sessions were open-ended, relying on the facilitator to translate questions and clarify issues in real time. Aiming to gain valuable feedback on the questionnaire and its comprehension, one-on-one shop visits with Women Entrepreneurs allowed us to ask our questions, identify shortcomings and knowledge gaps, and use our better understanding of the questionnaire scope to rewrite answer options to better reflect the user experience.
Phases of Translation
To anyone who’s taken a business assessment, you’re familiar with jargon. The technicalities of business terminology often create barriers for assessments written in someone’s native tongue. While our first content-focused pilot testing was translated on the fly, we didn’t realize that there was actually double translation taking place: One in language and the other in terminology, often changing how we pose technical questions, such as “Which transactions does your business collect?” into the Hindi version of “How do you take money?”. In these questions alone, we’re beginning levels of teaching and breaking down bits to fix and understand the experience of the business and its functions. While we collected data on the diverse answers and experiences of women, we didn’t consider the larger scope of language and comprehension, and how questions matter.
Standard Translation for assessment generally follows three key steps…
Step1. Forward translation
This refers to the translation from the language of the research team to the local language(s). This process can take a few days to a few weeks, depending on the complexity of the questions in the survey instrument (Avnish, pg1).
After more than 20 one-on-one piloting sessions, we began review sessions, expanding answer options and adjusting scoring. What are women telling us? Yes, we took that into account, but how were they saying it? It wasn’t our key objective. It was only after we agreed on the contents of the questionnaire that we then moved on to initiate the process of taking our English written questionnaire and sending it to app developers to be translated

Before deploying our questionnaire in its digital Hindi format in the field, we first tested our tool internally with our team. Working with our program managers and field staff, people who work day in and day out with our target base, we collected a great amount of valuable feedback. Questions and terms were only those that were too complete, an obsolete couple of words, and so questions were altered and adjusted. It wasn’t until our first round of piloting with groups of 20+ women entrepreneurs that we realized that how questions were worded mattered as much as what was asked.
English business jargon that had been translated into proper, traditional, rarely used Hindi made the questionnaire confusing in three ways. Needless to say, Aarti and — we’re not the only victims that day. Our first set of piloting, group style with a facilitator assisting every 5 participants, revealed extensive issues in questionnaire comprehension, with participants often relying on one another to understand the questionnaire as our staff flurried to answer questions and collect all of the feedback. The problem? We had only done one function of the three-fold translation process.
Step 2. Back translation
“Once researchers receive the first translation, they send only the local language version to a different translator, who translates it back to the language of the research team” (Avnish, pg1).

Photo credit: Author
With digital piloting taking place in 5 separate sections, covering over 65 participants, we quickly realized the questionnaire language needed to be altered. After each session, the data information of facilitators would report on which terms were obsolete or incomprehensible. For instance, business could be written just as business because women understand that better. But we also took note of the ways that the actual questions caused confusion. While our field facilitators recognized some of the confusing terms, we were far from capturing the vocabulary needed for comprehension in diverse regions across Delhi.
Regrouping after the digital pilot, it was clear to the team that serious alterations had to be made. But by taking the finalized version of our Hindi questionnaire, we then had one of our project managers, our field facilitators with translation expertise and years of experience with nano enterprise in rural, urban, and peri-urban spaces, to translate the assessment. Taking the feedback from our piloting sessions and revising our most finalized version of the Hindi questionnaire into a more comprehensive vocabulary, aiming to use words that are part of everyday language, rather than focusing on accurate Hindi translation. The changes were significant.
- Reconciliation:
“This refers to the process of comparing the original questionnaire to the back-translated questionnaire. In this stage, researchers should highlight any discrepancies and categorize them as either minor (like wording issues), or significant (like changes in the meaning of a question)” (Avnish).

Before deploying for a second round of digital piloting, we did back translation. Seeing the ways in which the terminology needed to be explained and ensuring that the questions were still collecting the intense insights and recommendations. Working with the team to discuss discrepancies in the two versions, making sure to reconcile them. To be frank, the differences were stark. Working with the pilot team, we had to revisit the way we explain questions, asking ourselves, “What does comprehension really mean?”
Lucky for us, the nature of the Enterprise assessment tool is Unique. An instrument that aims to fill the gap between tools that assess the individual capabilities of an individual with those that measure the overall success of an enterprise. After our first digital pilot, we revisited the purpose of an entrepreneurial assessment for women operating businesses at the last mile. Its main aim? Being a tool that can teach. A tool that can enhance one’s understanding of themselves and that of their business. A tool that can grow and expand with the user, first asking them baseline simple questions about savings and then expanding if they demonstrate understanding to ask more technical questions about banking and financial practices.
Key Learnings
Our work with the enterprise assessment reaffirmed a critical lesson: comprehension is central to effective tool design. Translation isn’t just about words—it’s about how meaning is understood and lived by the people we hope to reach. Through piloting, back-translation, and reconciliation, we learned that meaningful questions must speak the language of the user’s experience, not just their dialect. By embracing multiple rounds of piloting, feedback, and back-translation, we learned to see our tool not as a finished product, but as a growing, adaptive resource. This journey would not have been possible without the strength, patience, and dedication of our ACCESS Development Services team. Their willingness to test, revise, and refine ensured we addressed every gap, no matter how small. We are proud of their relentless commitment to creating a tool that not only measures but empowers—and we remain dedicated to this process as we continue improving the tool for the women it was built to serve.
Works Cited
Aizawa, Ikuya. The role of language on assessment outcomes: an analysis of calculation and explanation questions in science classrooms. Routledge Taylor and Francis Group, 2024. Taylor and Francis online, https://www.tandfonline.com/doi/full/10.1080/02602938.2024.2353865#abstract.
Avnish. “Questionnaire Translation | Dime Wiki.” Dime Wiki, 13 April 2021, https://dimewiki.worldbank.org/Questionnaire_Translation. Accessed 21 July 2025.
Depka, Eileen. “What a Difference Our Words Make! Asking Questions that Require Understanding.” All Things Assessment, 14 November 2017, https://allthingsassessment.info/2017/11/14/asking-questions-for-deeper-understanding/. Accessed 21 July 2025.

