Partner Branded Page

After handing off all screens to the Devs, the tasks are monitored via Jira according to the workflow below.

Disclaimer: The above system is not created by me but a replica to view a visual breakdown of how each task is managed while creating Partner Branded Pages

The Life Cycle of a task

💡Starting a Task

Task starts at OPEN status. From here:

1. If the task is not determined as a potential bug or has already been implemented, it will be shifted to CLOSED status.

2. If the task is taken up by the Development team, it's status will be shifted to INVESTIGATION IN PROGRESS.

🔁Task Development & Iterations

Task continues at INVESTIGATION IN PROGRESS status. From here:

1. If the Development team discovers some potential implications to the design or if Design team discovers that some designs needed to be edited or added, task's status will be shifted to PENDING SGI CLARIFICATIONS. 

2. Once implications have been resolved either via quick meetings or once designs have been created, task will be shifted to INVESTIGATION IN PROGRESS status

🖌️Work in Progress

Once all clarifications are addressed, the task continues at IN DEVELOPMENT status where the Development team will develop the feature onto a testing site. This testing site is a replica of the actual site but filled with dummy data for easy testing of features before they are deployed to the actual site. From here:

• Once the Development team has completed development of the task on the testing site, the task status will be shifted to IN UAT.

🧪Testing Phase

Once all developments to the test site are completed , the task continues at IN UAT status. The Design team will check the according to the Acceptance Criterias(ACs) listed within the task in the testing site. From here:

1. Each AC of the task will then be video recorded to prove that the feature has been checked. Each video then be listed under the comments section of each task. (Labelled with Header: UAT Verified)

2. If there are some bugs discovered during testing of ACs, the task status will be shifted to PENDING CLARIFICATIONS

   • Development team will then to look into and fix discovered bugs. Task's status will be shifted to FIX IN PROGRESS.

     • if no bugs are discovered on Development team's end, task's status will be shifted back to IN UAT. 

     • if discovered bugs are fixed, task's status will be shifted to IN UAT. Design team will need to do another check of the ACs

3. Once all ACs are checked, task's status will be shifted to UAT Passed.

4. At a planned date, the Development and Design team will then schedule a date and time for a deployment of this task into the actual site. Task status will be shifted to AWAITING DEPLOYMENT.

   • At this point, an announcement of the actual site going on maintance will be sent to all relevant teams who maybe using the actual site if necessary

Reflections

• Building clarity in my designs

When I first started managing Partner Branded Pages, I went in thinking my designs would speak for themselves. I quickly realised, however, that handing over "just Figma screens" left my developers in a tough spot. They were often stuck guessing which buttons to update or which specific colours to swap. To fix this, I started adding mini UI notes and documenting every interaction in detail. Moving beyond just the visuals to provide a clear "how-to" for the build has been a game-changer. Additionally, it takes the guesswork out of the development process and ensures the final product actually matches the acceptance criterias.

• Finding out all edge cases in a feature

To ensure a well-rounded feature release, every edge case must be thoroughly evaluated. For the Partner Branded Pages, we are addressing the following ones:

• External Redirection: Users registering via Deep Tech Central (DTC) must see a redirection screen. This informs them they are leaving the current site, preventing confusion.

• Access Control: Organisation users viewing a module they did not create should be restricted from viewing user activity data; this data should only be visible to the module's creator.

• Empty States: We need to define the 'basic user' experience for instances where no module listings exist—specifically, whether they encounter a themed empty state or a standard screen.

• Persistent filters:  After applying filters, users should be able to see the applied filters when toggling back to the same listing from a separate page.

The above list isn't everything, but it shows why I need to think through these scenarios early on. It’s the only way to really nail the feature and make sure all our bases are covered.

• Attention to detail