This week has been one of those quieter, reflective periods in grad school—a welcome contrast to the fast-paced rhythm I’ve grown used to. There’s a lot to unpack, especially when it comes to shifting gears from constant creation to taking a step back, planning, and documenting. It's been a gradual adjustment, but it feels like a necessary one.
The Dialogue Shift in Grad School
Something I’ve been noticing more and more is how much grad school emphasizes communication—whether it's with peers, professors, or even just within the projects themselves. In undergrad, the focus was always on doing, on getting things done and moving on to the next task. Now, it’s much more about understanding the why behind what I’m doing, documenting it, and thinking about the long-term impact of my work.
It’s a slower, more deliberate process. And while I sometimes miss the rush of immediate creation, there’s value in this approach. It's like I'm being asked to pause and think deeply, rather than just reacting. There’s more conversation around design decisions, and that’s led to some meaningful insights I might not have had otherwise.
A Quiet Week of Starting New Projects
This week has been a bit quiet—most of the bigger projects wrapped up last week, so this was more of a transitional period. It was a chance to reset, plan for the upcoming work, and get things in order before diving back in. I think grad school has these ebbs and flows that are different from undergrad, where things never really slowed down.
It can be a bit of a challenge mentally to manage these quieter weeks. There’s a part of me that feels like I should constantly be doing something, producing something. But I’m learning to appreciate these moments of calm as necessary steps in the process.
Motion Capture Project: Working as a Team
One of the projects I’m really excited about is the Motion Capture Project. I’m working with three other grad students to create a series of motion capture shots. The concept revolves around a small protagonist, similar to It Takes Two, who is being assisted by a larger character, like in Ghost Giant.
The reason we chose this design is that it allows us to experiment with scale in motion capture, which adds a unique challenge. It’s also giving me the chance to work with a larger group, navigating the complexities of the software together. Collaboration has been a key part of this process, and we’re all learning a lot from each other’s strengths and perspectives.
BallroomXR: Innovating VR Dance Training
Another project I’m focusing on is BallroomXR, which aims to create a VR ballroom dance trainer. The idea is simple—many dancers don’t learn well from reading books. I wanted to create something that would help people review moves in a more interactive way, without the need to refer back to written guides.
As I started researching existing applications, I found that the VR dance space is still in its early stages. Projects like The New Salsa Academy provided some inspiration, but I noticed gaps in the way motion capture was being utilized, especially in terms of execution. I also explored VRChat's The VR Dance Academy, which has live community lessons, but there's little support for asynchronous, solo practice.
Design Iterations and Decision-Making
This week, I spent a lot of time thinking about who would use BallroomXR and how. I mapped out a user journey and began sketching ideas for the menu system that would allow users to navigate through different dance moves.
One of the biggest challenges was deciding between various menu styles. I explored hand menus, environmental menus, and float menus, drawing a lot of inspiration from Lucy Carpenter’s blog on VR Menu Patterns. After sketching things out and reflecting on the feedback I received, I narrowed it down to two final options; The Menu Based Design and The Preview Based Design.
The first was more stylized, with different layouts for each section. It allowed for creativity but also felt a bit cluttered when considering how many options there would be on each page. The second option was more uniform, offering a cohesive design that would be predictable and easy for users to navigate. In the end, I opted for the latter—it felt like the cleaner, more practical choice, especially for an application focused on learning.
Core Features Moving Forward
For now, here’s what I’m aiming for with BallroomXR:
Must-Have Features:
A dancer demonstrating a single move.
A lesson presented by the dancer for that move.
The ability to dance alongside a virtual character, either as lead or follow.
Background music for the dance session.
Additional Features I’m Considering:
Demonstrations of multiple moves.
The ability to dance alongside virtual dancers.
Feedback on dance performance.
A freestyle mode that incorporates several moves.
I’m keeping the focus narrow for now to avoid feature creep, but I’m open to expanding as the project progresses.
Algorithmic Rhythm: Pre-Planning for Success
For my Algorithmic Rhythm project in my 6400 Graduate Design Studio class, I’m diving into live-time motion capture. This week has been all about choosing the right technology and laying the groundwork for the project.
Why Live-Time Motion Capture?
I decided on live-time motion capture because it aligns well with my research interests, particularly in how body-tracked data can be integrated into interactive media. It also ties into my work as a Graduate Research Assistant, where I’m already working with motionless tracking systems. This technology has the potential to enhance some of my current projects, like BallroomXR, by allowing for real-time analysis of a dancer's performance.
The Importance of Planning
I spent a significant amount of time this week on pre-planning and creating a detailed report layout for the project. This is a shift for me—last time, I jumped straight into the work without much of a roadmap, and I ended up feeling a bit scattered. So this time, I’m taking a more strategic approach, making sure I know exactly what steps to follow and where to focus my energy.
Key Takeaways from the Week
Documentation as a Design Tool
One of the biggest lessons I’m taking away from this week is the importance of documentation. In undergrad, I tended to think of documentation as an afterthought—something to do at the end of a project. Now, I see it as a fundamental part of the design process. Writing things down forces me to articulate my ideas clearly and helps me spot gaps or inconsistencies in my thinking. It’s also a great way to keep track of my progress and reflect on my decisions later.
The Value of Prototyping Quickly
Another key takeaway came from my work on the BallroomXR menu design. By sketching out multiple iterations quickly, I was able to get feedback early and adjust my design accordingly. This process helped me avoid getting too attached to a single idea and allowed for a more thoughtful final design.
Final Thoughts: Shifting Gears in Grad School
Overall, this week has been about adjusting to a different pace—one that values planning and reflection as much as action. It’s a shift that I’m still getting used to, but I can already see how it’s helping me approach my projects with more clarity and purpose. Grad school is teaching me that not every week needs to be about tangible outcomes; sometimes, the most valuable work happens behind the scenes, in the planning and the conversations.
I’ll be taking these lessons forward as I continue to navigate the balance between making and thinking, between action and reflection. More updates soon, as these projects continue to evolve!
Comments