From Confusion to Clarity: First Steps in Sustainability Consulting

My practicum project this semester sits at the intersection of capital markets and sustainability policy. We are conducting a systematic review of ESG guidance documents from exchanges in G20 countries, benchmarking them against a set of model guidance standards, and developing evidence-based recommendations to improve their relevance and impact. Coming in, I expected this to be a relatively straightforward research exercise. That assumption was quickly challenged.

It took me longer than I anticipated to understand what this project was actually asking us to do. On the surface, the task seemed clear: read guidance documents, compare them, and write recommendations. But as I dug deeper, I realized I did not fully grasp what "comparison" meant in this context. Was it about the topics each exchange covered? The structure and readability of their documents? Whether they included training resources or capacity-building tools? The answer turned out to be all of these and more. I spent considerable time reviewing background materials and studying how previous cohorts had approached similar projects. That process forced me to move beyond a surface-level understanding and think about the analytical framework we would need to make the comparison meaningful rather than merely descriptive.

The most transformative experience so far has been drafting the project scope document. I volunteered to write the first version, and I approached it the way I would approach a solo assignment: research thoroughly, write carefully, and present a polished draft. What I delivered was technically competent but reflected only my own interpretation of what the client needed. When my teammates reviewed it, their comments revealed gaps I had not considered. One teammate questioned whether our research methodology was specific enough to guide our day-to-day work. Another pointed out that the timeline did not account for potential scope changes after client feedback. These were not minor edits; they reshaped how I understood the project itself. The final version was a genuinely collaborative product, and the process taught me something I had not fully appreciated before: in consulting work, shared understanding is not a nice-to-have but a prerequisite. A scope document written by one person, no matter how thorough, cannot capture what four people thinking together can produce.

As we now prepare for our first formal client meeting, I feel that the early struggles were necessary and valuable. We have a clear research question, a structured methodology, and a realistic phased timeline. More importantly, I have shifted how I think about my role in a team. I used to believe that contributing meant delivering finished work; I now see that contributing also means asking the right questions, inviting pushback, and being willing to let a draft evolve beyond my original vision. The work ahead will be intensive, involving close analysis of roughly twenty guidance documents, but I trust the foundation we have built together. I want to carry this collaborative mindset into every client interaction and every phase of the project going forward.