My recurring tasks within the project group are mostly coordination, tracking, and communication-oriented rather than direct technical research work. The most consistent tasks I have been doing include:
- attending project and related course meetings,
- listening for updates, blockers, and next steps,
- tracking what each person is working on,
- organizing progress into weekly trackers or summaries,
- following up on what changed from one week to the next,
- noting where work appears blocked or unclear,
- and helping maintain continuity between meetings, weekly reports, and action items.
Because this is a research project, work can move unevenly from week to week. That means one important part of my role is making sure progress does not disappear into scattered conversations. I try to convert updates into something more visible and structured so that the team’s work over time is easier to follow. I also see part of my recurring role as helping with onboarding and context-building within the group. Even when I am not solving technical problems directly, I can support the project by improving clarity around who is doing what, what the current priorities are, and what follow-up is needed.
I am assessing my role primarily through whether I am improving clarity, continuity, and accountability within the project. Because this is a technical research project, I do not think the best way to judge my role is by claiming direct ownership of technical breakthroughs. Instead, I think my effect should be assessed through questions like:
- Are updates being captured more clearly?
- Are next steps more visible after meetings?
- Are blockers being noticed sooner?
- Is there better continuity between what was said last week and what is being done this week?
- Is it easier to understand who owns which task?
So far, I think my role has been most useful when I help reduce ambiguity. In a research setting, it is easy for important details to remain informal or spread out. By organizing updates and turning them into clearer trackers and follow-ups, I can support the team’s ability to stay aligned. I also assess my role by whether I am making it easier for others to do their work. If researchers spend less time reconstructing context and more time focusing on experiments, writing, benchmarking, or debugging, then my support is adding value.
- Technical complexity: the project is highly specialized, so it can be hard for non-research coordination work to keep up with the technical details.
- Uneven update cadence: research work does not always produce neat weekly outputs, so some weeks have clearer progress than others.
- Scattered context: important information can live across conversations, reports, links, and code-related updates.
- Bandwidth constraints: team members are balancing research, writing, experiments, and other obligations, which can make coordination harder.
- Translation challenge: it can be difficult to convert complex research updates into simple, trackable project status.
- The group is actively working on concrete technical tasks rather than staying abstract.
- There have been identifiable next steps around experiments, benchmarking, and writing.
- Progress can be seen across weeks when updates are collected and tracked.
- There is enough structure in the work that coordination can meaningfully help.
From my perspective, one success in my own role is that I have been able to create more continuity around updates and tasks than would exist if everything stayed only in conversation form.
How are you collaborating with stakeholders to ensure your role is supporting and motivating the group?
I collaborate mainly by staying close to the information flow of the project and trying to turn that into useful support rather than passive observation. This includes:
- paying attention during meetings to what each person is focused on,
- noticing when tasks need follow-up,
- keeping progress visible through summaries and trackers,
- and communicating in a way that supports clarity rather than adding pressure.
The stakeholders I am collaborating with include researchers on the project, my co-manager, course leadership, and the broader HAAG structure around reporting and progress. My goal is not to micromanage technical work, but to support the group by improving organization and reducing avoidable confusion. Motivation in a research group is also different from motivation in a traditional business project. People are often motivated by progress, clarity, and the feeling that their work is connected to a larger direction. Because of that, one of the best ways I can support motivation is by helping make progress visible and making next steps feel clearer.
Most of the feedback I have received so far has been indirect rather than formal. In other words, I have learned more from how the work is functioning and what the group seems to need than from explicit performance reviews. The clearest signals so far suggest that coordination support is useful when it helps:
- make updates more visible,
- connect meetings and weekly reporting,
- and keep tasks from getting lost.
At the same time, one implicit lesson I have noticed is that coordination only helps when it stays lightweight. If the process becomes too heavy, it risks creating more burden than value. That is useful feedback for both my project manager role and my initiative work. I would describe the current feedback environment as one where expectations are present, but detailed role feedback has been limited. Because of that, part of my job is to keep learning from observed needs and adjust accordingly.
What plans do you have for enhancing your role as project manager with the remaining time in the semester?
For the remainder of the semester, I want to make my role more useful in a few specific ways.
- Make my tracking more consistent from week to week by using a repeatable structure for current task, status, blocker, owner, and next step.
- Move from simply recording updates to surfacing the most important ones more clearly.
- Identify which items need follow-up, which items are blocked, and which items may need leadership attention.
- Connect my initiative work to actual project needs by applying some of the same project-clarity principles where helpful.
- Become better at translating research activity into project-management language without oversimplifying the work. That would make it easier for leadership, managers, and others outside the immediate technical loop to understand progress.
The main support that would help me most in this role is:
- clearer expectations about how much initiative implementation versus project coordination is expected by mid-semester,
- timely updates from project stakeholders so that tracking reflects the current reality,
- occasional validation from a lead or advisor on whether the information being tracked is the most useful level of detail,
- and a willing pilot context for testing onboarding and project-clarity improvements in a realistic way.
I would also benefit from continued clarity from course leadership on what good enough looks like for the initiative at this stage. Since the semester timeline is limited, it is important to focus on a realistic pilot and a well-documented procedure rather than trying to build a large system too quickly. Overall, I think I can contribute the most when expectations are clear, the scope stays realistic, and I continue focusing on coordination work that genuinely reduces confusion for the group.