Blogs by Colt

Author: Colt Cruz
Date: January 25, 2026

This week was heavily focused on structure and documentation rather than development or creative output. Most of my time went into reviewing the design document, making edits, and filling in missing sections that needed clarification. Alongside that, I spent time working through how the Jira board is organized and what role it plays in keeping the project moving forward. Compared to those two areas, wireframes were a lower priority overall, even though I ended up spending a significant amount of time on them.

The design document was the main focus for me this week. I completed a full review, made edits for clarity, and added content where information was missing or underdeveloped. Going through the document in detail helped surface gaps in scope and intent, especially since the product has not yet been formally pitched. Without that shared context, some decisions feel disconnected, which makes it harder to confidently plan technical systems around them. Addressing those gaps early felt necessary to prevent confusion later in the project.

Jira was also a major component of this week. I’m glad that one of my teammates took the initiative to figure out the board structure, since Jira was one of the main requirements for this phase outside of finalizing the design document. Having the board set up properly made task tracking clearer and helped establish a baseline for accountability, even though consistent usage will still be important moving forward.

While wireframes are not the most critical piece at this stage, I ended up working on them largely on my own to keep progress from stalling. Treating them as a rough draft rather than a finalized deliverable allowed me to focus on basic flow and structure without overinvesting in visuals. At this point, they function more as a reference than a driver of decisions.

Overall, this week highlighted how uneven contribution can impact momentum, but it also reinforced the importance of stepping in where gaps exist. Even when the work is less visible or less enjoyable, maintaining forward progress through documentation and process is essential. Establishing clarity now should reduce friction and rework once development begins.