Design

Service Design methods to support service and content-based improvements

16 Jul, 2021

Reflecting on designing a watch party for UX Brighton Watch the UX Brighton watch party for yourself using this playlist on YouTube (took place on 13th April 2021) Look at the schedule and information for the event which was provided as a Google Doc Visit the Mural board that I used to guide my design and then reflect on my experiences Check out the video bingo mini challenge (H5P interactive activity) Edited Vlog Transcript Hi folks, I know it’s been a while. So, yeah basically what I can say is I’ve had a couple of really paperwork intensive months. I ran a watch party for UX Brighton because I presented about a few of the challenges I’d found through working on some discovery at my workplace. The suggestion was that perhaps we could do a UX Brighton watch party and that might provide me with an opportunity to experiment to try out some things that I couldn’t try out at work and to get some really helpful critical feedback. So, I’m really delighted to say that I got that opportunity because I really did get amazing feedback and I have since used the learning that I gained from that particular watch party to feed into my professional portfolio, and I’ve also used it to think really critically about how I talk to staff about watch parties how I encourage them to onboard people during watch parties.

4 Jul, 2021

At the end of my last entry I outlined my discovery that there was an app building company called Bubble, which would likely lead to brand confusion. As a result I decided to go back to some of the ideas on my earlier sketchbook page and consider other possibilities that would tackle some of the same goals. The following company traits need to be suggested by the name:

13 Feb, 2017

On this page of my sketchbook I used a dice rolling exercise (Barnard & Briscoe, 2016) to explore different name combinations for the potential company. Initially I gravitated towards BubbleHome as a concept.

11 Feb, 2017

Greetings! I have decided that I would like to keep up my reflective writing activities during IDM22. This is due to my recent experience on the web development module and also thinking back to when I took IDM21 (seems so long ago now!). In both cases it was an immensely valuable venture.

4 Feb, 2017

\[caption id="attachment\_381" align="alignright" width="288"\]\[/caption\] Altering the Flickity Carousel/Timeline So changing the height of the Flickity carousel used for the patient timeline meant that the “dot” buttons had to be moved upwards otherwise they would be off the bottom of the visible area on most standard screen sizes. For reference, I have included a long screenshot that I made of the site prior to this work, on the right. So I decided that the dots should reside on-top of the carousel and then they would also be spatially connected to the navigation of the timeline. This is not really how Flickity carousels are really designed to exist (metafizzy, 2016), but it is closer to the original inspiration for my site the DuckDuckGo about page (DuckDuckGo, 2014). The main issue that I ran into was that the carousel needed to resize itself dynamically and I had media queries which hid the dots on mobile devices (as they were no longer very useful as buttons at that size). However, as the dots themselves are rendered automatically by the JavaScript, they were rendering much more quickly than the resizing. So I upon sizing-up a responsive browser window the dots and timeline appeared on top of everything and looked awful. I tried everything I could think of to fix this issue. I attempted to delay the dots in the JavaScript. I also tried writing a script which watched for the window size. I tried positioning the dots so that they moved upwards. I also tried creating condition code which watched for various conditions to be met prior to triggering the dots. Things I wrote worked to an extent, but not sufficiently or reliably enough to depend on them. In the end I had to temporarily hide the dots by setting them and the timeline to ‘display: none’. I also had to hide the spot where they generated by moving the about section upwards. Essentially the solution’s analogue equivalent is that the rabbit is being hidden in a compartment of the hat the whole time (oh wait…is that how they do it?). Performance Issues I am actually grateful that all of this happened as once I had cracked the rendering issue I realised that there were some major performance issues with the carousel/timeline. It took a bit of time to get to the bottom of it, but in the end I realised that it was the long svg that I had included to indicate the patient’s anxiety levels. Through testing in multiple browsers, on Mac, PC and mobile I realised that the image also wasn’t loading anywhere other than in Chrome for Mac. Everywhere it was just gumming up the works. I reassessed the need for the anxiety level gauge/image and decided that it was important to keep it. So through trial and error I ended up loading with an image tag in the html as a very, very long svg. This is the only svg in the site that I could not optimise as it resulted in optimisation errors because it was too long dimensions-wise. Also, I realised that I did not really want to optimise it as I would result in losing the drop shadow detail which I had added to a new version of the design.

16 Jan, 2017

I knew that all of that work that I did on polls would come in handy at some point. The time arrived, as displaying data was something that seemed important from the beginning, to support the goals for the project. I wanted to support the information about ‘UK smart device ownership’ with some data. Having spent quite a bit of time looking at polling options and trying things out, I felt sure that the the Google Charts api (n.d.) would give me the level of interactivity and customisation required.

7 Jan, 2017

This journal entry represents a mammoth effort to add high-quality content to the site. I developed and added the patient story. This was based on a characteristics list which I worked through rather vigorously on the afternoon of the 25th. This is still in handwritten form, so I will link to it as a google doc later on. I have included some key references for that process below. I want to highlight the National Joint Registry (2016) data, which was particularly helpful during the process of defining the patient story. Also the specific images that I used will be cited on the portfolio site (including cc0 works; royalty-free works) as I feel it is always very important to include the provenance of images in any context, but especially when engaging in a thought process based on a fictional patient/nurse interaction.

2 Jan, 2017

I have been plugging away at the portfolio site with the primary aim of getting a semi-functional prototype version to Dr. Theo Fotis on Monday 12th of December. There is a still a huge amount of stuff to do, fix-up and streamline I will add these tasks to my Trello board. This journal entry provides a rundown of the decisions that I have this week.

11 Dec, 2016

This week I completed some major fix-up on my grid. Remember when I thought that it was almost fixed? Well I was wrong. In fact I ended up recalculating the whole thing and basing it on a single column being 65px or 6.5% in width. Happily it is now working exactly as I need it to (Mozilla Developer Network saved the day againhttps://developer.mozilla.org/en-US/docs/Learn/CSS/CSS_layout/Grids#Creating_a_fluid_grid - I am going to up my donation this year).

8 Dec, 2016