I would like for you to improve my writing about my thoughts relating to my product. I need you to improve the grammar, expand on important points, and structure the thoughts better.

Here are the thoughts grouped by the time where I have thought about it:

## 💭 Thoughts

### 🕗 8:00 AM

Yesterday, I made the realisation and decision that I could probably just focus on teachers. There are still going to be experiences that needs to be developed for students. However, instead of building these experiences with a student-first mindset, we will have a teacher-first mindset. Meaning, these experiences will be developed to enable the teacher-focused experience we are developing. However, as we automate teacher experiences, the offering for students becomes greater that it will eventually evolve into a product that caters for students. But, the product will evolve from serving teachers into serving both teachers and students by focusing only on teachers. How does this make sense? By automating teacher activities one-by-one, we are essentially building an autonomous teacher. An autonomous teacher would be the core product for students. Hence, by building for teachers, we will develop an autonomous teacher which will serve students.

I am building for four teacher-focused experiences:

- Finding Experience
- Submission Experience
- Marking Experience
- Creation Experience

And one student-focused experience:

- Collection Experience

I have an MVP of Finding and Submission Experiences have been built. Next is building an MVP for the Marking Experience. Followed by an MVP for the Collection Experience. And finally, an MVP for the Creation Experience. Once I have an MVP for each experience, I will begin optimising them holistically by optimising for use cases/jobs-to-be-done.

Building an MVP for Marking and Creation Experiences will each take a week. And building an MVP for the Collection Experience will probably take half-a-week. This means, I should have an MVP version of this latest iteration of the product in two-and-a-half weeks which coincides perfectly with our Cebu trip. After the trip, I will spend until the end of week fourth week building the Subscription Feature Set. By this point, I am four weeks into the quarter, which means I have nine weeks left for the year. I’ll spend four weeks optimising for the use cases/jobs-to-be-done. And then, I will spend the rest of the year building the growth engine. After the growth engine, my attention will shift to collecting emails and expanding our library. The goal is to finish email collection and library expansion before school year 2025 starts. After that, all my attention shifts to the Class Experience.

### 🕤 9:30 AM

The goal for this week is to build the MVP for the Marking Experience. Currently, to get to the Marking Experience, the user will have to select from the submissions that have been made. I even question the importance of the Marking Experience. I was initially thinking that the Marking Experience will be used heavily. But, in a situation where teachers trust Eh-Llie, the importance of the Marking Experience diminishes. Maybe, I should lean on the fact that AI will get significantly better, and having a simpler Marking Experience will be optimal for myself and the teachers. It allows me to think of a simpler experience. All right, I made a decision, I will build Eh-Llie with agents and automation in the forefront. The primary user flow will be the autonomous experiences. Manual experiences will be secondary and will not be included in the primary user flow. Manual experiences will be fork on the primary user flow. The use of manual experiences will indicate insufficiencies in our autonomous experiences. But instead of determining an optimal manual experience, I should focus in optimising the autonomous experience.

This mindset has resulted in significant reduction in the role of the Marking Experience. It’s primary purpose now is to be viewer with editing capabilities. It is no longer a dedicated page, but rather, it is supporting page. I am thinking more of a Google Doc style experience where questions and answers are arranged in a vertical scrolling experience accompanied by a dynamic right panel which displays any grade and feedback the teacher has made.

### 🕥 10:30 AM

- [ ]  Build the MVP for the Marking Experience

The marking experience has three components, table of contents, question and answer sets, and feedbacks. Table of contents showcases the assessment structure and allows for automated scrolling. Question and answer sets showcases the student performance data. Feedbacks showcases the feedback that has been made for the question and answer sets in focus.

The behaviour of feedback is to showcase all of the feedback that has been made upstream of a branch. It is also interesting to think about how we will handle situations where submission is made for a ancestor question but none for the descendent questions. When the table of content for the descendent question with absent answer is clicked, ideally, we take them to the ancestor question. Maybe, when we know that the answer applies to the rest of the branch, we can just add all invisible headings that the table of content navigates to. It might also be worth finding the furthest descendent so we can display all of the relevant feedback. For example, let’s say we have Q1, Q1.a, Q1.b, Q1.c and a submission has been made for Q1 and for all descendent. We will have headings invisible of Q1 and its descendent so that when the user press Q1.c on the navigation, they are taken to Q1 submission which is correct. We will also have feedback displayed for all descendent and their ancestors. For the feedback component, teachers can write a feedback for each question - having the option to write feedback for all questions in the tree.