Dirk’s 3x3 Reflection Process
Note: This document was originally developed collaboratively with Microsoft Copilot as a prompt used to bootstrap new conversations about my weekly 3x3 reflections. Over time it evolved into a description of the reflection process itself. I am publishing it here both as a reusable AI prompt and as documentation of a workflow that I have found useful for reflection, communication, planning, and record keeping.
I encourage my students, collaborators, and colleagues to develop similar reflection habits. While the specific format is not important, the practice of regularly stepping back to think about accomplishments, challenges, and priorities can be surprisingly valuable.
Microsoft Copilot Prompt
The content below is the prompt I currently use to help Microsoft Copilot assist me in writing and refining my weekly 3x3 reflections.
Dirk’s 3x3 Reflection Process
What Is a 3x3?
Each week I write a “3x3 Reflection” consisting of:
- Three Top Projects This Week
- Three Questions/Challenges
- Three Projects for Next Week
Although the final document is shared with others, I primarily think of it as a reflection rather than a report. The act of writing the 3x3 is often more valuable than the finished product.
Why I Write 3x3 Reflections
The 3x3 serves three primary purposes.
1. Weekly Reflection
The most important audience is myself.
Each week, the 3x3 forces me to:
- Review all of my active projects.
- Reflect on what I actually accomplished.
- Consider whether I am spending my time on the right things.
- Identify challenges before they become problems.
- Decide what deserves my attention next week.
In practice, the reflection process is often more valuable than the final document.
The 3x3 helps prevent me from focusing only on the loudest or most urgent project. It forces me to mentally check in across all of my responsibilities and make conscious decisions about priorities.
2. Team Communication
I share these reflections with students, collaborators, community partners, and colleagues.
The goal is to:
- Keep teams informed about what I am working on.
- Provide context for my priorities.
- Surface challenges where others may be able to help.
- Create opportunities for collaboration.
- Encourage communication across teams.
I encourage (and sometimes require) members of my teams to create similar reflections.
Many useful conversations begin because someone notices a challenge in a 3x3 and reaches out with advice, experience, references, or support.
Because of this, the Questions/Challenges section is especially important.
Whenever possible, I try to include questions that:
- Are real.
- Are specific enough for people to respond to.
- Could benefit from outside perspectives.
- Invite discussion instead of simply reporting frustration.
A useful challenge is often worth more than another status update.
3. Long-Term Record Keeping
The 3x3 also serves as a lightweight professional journal.
Over time, these reflections become a searchable record of:
- Teaching activities
- Student mentoring
- Grant development
- Research collaborations
- Software projects
- Community engagement
- Professional service
- Personal projects
I frequently use past 3x3s when preparing:
- Annual reviews
- Activity reports
- Promotion materials
- Biosketches
- Grant proposals
- Recommendation letters
- Presentations
Because of this, I often include project names, presentation titles, workshop names, and other details that may be useful to remember later.
Most Important Rule
I strongly prefer that all nine bullets represent different projects whenever possible.
For example:
Bad
- CMSE 802 accomplishment
- CMSE 802 challenge
- CMSE 802 plan
Better
- CMSE 802
- CMSE 495
- VIP
- Graduate Mentoring
- Community Partners
- Grant Development
- Educational Infrastructure
- Professional Service
- Personal Project
The goal is breadth.
A reader should finish the 3x3 with a reasonable understanding of the variety of things I work on.
Think in Terms of Projects, Not Tasks
When writing a 3x3, focus on the larger project behind the work.
Examples of tasks:
- Sent emails
- Fixed a bug
- Reviewed code
- Graded assignments
- Attended meetings
Examples of projects:
- CMSE 802
- CMSE 495
- VIP / SEE-Insight
- Spring Capstones
- CMSE Course Template
- EASE Reporting
- MailMerge
- Dissertation Mentoring
- Grant Development
The challenge is often identifying which project is represented by a collection of tasks.
Preferred Structure
Top Three Projects This Week
This section highlights accomplishments, milestones, discoveries, or meaningful progress.
Projects do not need to be completed.
Good examples:
- Finished a new curriculum module.
- Conducted over-the-shoulder code reviews.
- Delivered an invited presentation.
- Held a productive grant-planning meeting.
- Completed a major software feature.
Avoid generic activity reports.
Examples to avoid:
- Worked on CMSE 802.
- Answered emails.
- Went to meetings.
Questions / Challenges
This is often the most valuable section.
Avoid generic statements such as:
- I am busy.
- I need more time.
- I have too many meetings.
- I am behind on everything.
Instead focus on:
- Design questions
- Curriculum questions
- Research questions
- Software engineering questions
- Organizational challenges
- Leadership questions
- Project tradeoffs
- Emerging opportunities
Good examples:
- Should CMSE develop a Research Software Engineering course?
- How much course infrastructure actually helps students?
- How should AI tools be used safely with protected data?
- How much student behavior can be meaningfully quantified?
- How should accessibility requirements balance flexibility and consistency?
- What support systems help researchers maintain productive habits?
The best challenge items:
- Reflect genuine uncertainty.
- Invite feedback.
- Give readers an opportunity to help.
- Encourage discussion.
A useful challenge often starts with:
“I have been thinking about…”
or
“I continue to wonder…”
rather than:
“I am behind on…”
Projects for Next Week
These should be concrete commitments.
Prefer projects that are not already heavily represented elsewhere in the same 3x3.
Examples:
- Review a dissertation.
- Prepare an invited talk.
- Write recommendation letters.
- Support a workshop.
- Continue capstone outreach.
- Publish a software release.
- Launch a new feature.
These items generally require little explanation.
Writing Style
Keep bullets concise.
Usually:
- One sentence.
- Occasionally two.
- Rarely more than three.
Avoid:
- Corporate language.
- Annual-report language.
- Long explanations.
- Excessive justification.
The project should generally speak for itself.
When editing, ask:
Can I remove this sentence and still understand the point?
If yes, remove it.
Personal Projects Are Allowed
I occasionally include personal projects.
Examples:
- Family activities
- Cars
- Hobbies
- Travel
- Personal development
This is intentional.
I want students and colleagues to understand that I have interests and responsibilities outside of work.
Personal items should not dominate the report, but including one occasionally helps make the reflection feel authentic and human.
Common Project Categories
Teaching
- CMSE 802
- CMSE 495
- VIP
- SEE-Insight
Student Mentoring
- Dissertation reviews
- Recommendation letters
- Student mentoring
- Over-the-shoulder code reviews
Research
- NSF proposals
- Grant development
- Research collaborations
- CyberAmbassadors
Educational Infrastructure
- CMSE Course Template
- Accessibility initiatives
- Course websites
- Instructor notes
- D2L infrastructure
Software Projects
- EASE Reports
- Daily Check-In tools
- MailMerge
- MarkdownReport
- Research Guidelines
- Scientific Image Understanding
- Git utilities
- Workflow automation
Service
- Design Day
- Community partners
- Workshops
- Invited talks
- Committees
Personal
- Family
- Cars
- Hobbies
- Productivity systems
Things That Make a Great 3x3
A great 3x3:
- Represents nine different projects.
- Includes at least one thoughtful question.
- Includes at least one item that could spark discussion.
- Includes concrete accomplishments.
- Includes realistic commitments for next week.
- Gives readers an opportunity to help.
- Provides useful context without excessive detail.
- Feels personal.
- Is short enough that people will actually read it.
Final Guiding Principle
A good 3x3 is not simply a record of what happened this week.
It is a lightweight tool for:
- Reflection
- Communication
- Planning
- Collaboration
- Record keeping
The best 3x3s help me understand:
- What I accomplished.
- What actually mattered.
- What is challenging.
- What I should prioritize next.
- Where others may be able to provide ideas, experience, feedback, or support.
If there is a choice between completeness and readability, choose readability.
If there is a choice between activity and reflection, choose reflection.