This loads in really weird. Are you experiencing the same? You should be able to assign this to load in first.

I have all of the same feedback on this case study as the issues appear to be at the level of your template.

Images and all sections need to have responsive behaviour. Images all need to open in lightbox or new tab when clicked!

This area needs to stack as two columns doesn't work on anything smaller than tablet.

Same issue as above with all the remaining images on the site. They aren't responsive. Also they all need to open in ligjtbox or new tab.

Wireframes below flow off screen on smaller displays. I'd recommend stacking these.

Sitemap images is being stretch.

Persona image is unresponsive and needs to open in lightbox of new tab.

Same problem as other case study; not responsive.

one smaller devices these headings should just stack on top of the body text...the two panels doesn't work very well on narrow view ports.

There's some extra spacing above this heading on smaller devices...weird. Something is breaking.

The images here aren't responsive. They need to stack on smaller screens.

Also all images need to open in a light-box or new tab.

The persona image needs to be expandable in a light box or openable in a new tab.

Also this section is not responsive.

It may be worth putting background behind this chart so it's clear that it's an asset from your project and not editorialization. You could also probably step down a font size.

This section doesn't appear to be responsive.

Same comment as on your home page. On my super large display your line lengths are too long since there is no max set for your content area. It makes it really hard to read...I actually have to move my head left and right lol

"Email Me" might be more accurate to the resulting action. When I see 'Contact" I expect to be taken to a form.

I'm not sure you need this link and additional page since your home page has all of your work.

For each of these i'd reduce the text to just one sentence describing the solution. They will drill in to learn more about the process and your outcomes.

Nice hover effect!

On my 27" monitor there is very little margin and so your line lengths are really long. I'd recommend setting a max width for your content area so that beyond that point if a screen is super wide like mine it just creates more margin.

Love the before/after images below! Nice!

Same as above. Indicate which you chose on the image itself.

Which of the above did you choose here? Can you add a rectangle around it to indicate?

These should pop more! Maybe make these larger?

I recommend moving this text up before the sketches so that it provides context for them before the reader views them.

Because you used this green card treatment earlier for research insights I expect these to be insights from your usability test but instead they describe your process. Id recommend keeping this consistent and finding a different treatment for this info.

These wireframes look great btw!

It feels a bit wordy with these blurbs. Can they be shortened and summarized within the definitions of each of these features/pages?

Okay I see you've made them prominent here. I think that works well actually.

I feel like these should be highlighted or added to the above sentence since this is more specifically what they are trying to showcase via their site.

Also love this section! Makes it really clear that you aren't jumping to conclusions and weighing the user testing insights with other considerations. Very mature practice here.

This whole section where you are describing what you explored in your sketches and the decisions you made in doing so is excellent!

It's not clear here whether these and the things on the other two cards were in your design or if this feedback would lead you to update those designs. Can you add an iterations or next steps section to indicate what updates you have already made or what updates you would make or feedback you would continue to listen for in the future.

Try left justify!

The images are still quite small once you click on them and enter the lightbox. I'd recommend breaking these images up into 2 or more smaller sets so that when they are expanded they appear larger.

This is more accurately a set of user tasks.

A task is something that a user completes; sometimes using software (ex. "as a user, I want to sign in so that I can complete my order)

A workflow is how that user completes that task using the software (ex. first I click 'sign in' then I complete the form, then I confirm my information and am signed in)

A Task flow is a diagram created by designers to represent a workflow in low-fidelity 'boxes and arrow' type diagrams.

So here I think you probably want 'Workflow' since the 'tasks' you identified earlier have been solved for with the UI.

Re-phrase this to explain why you felt like usability testing would be a useful next step for this project and that to do so you created a prototype and usability test plan based around your hypothesis. You want to avoid making it sound like 'usability testing comes next and so that's what I did'.

This section is great!! It does a good job of finding that perfect level of detail.

The images to the right are kind of cut off/misaligned. Not sure what's going on there.

Make clear that this is existing press & hold so you are leveraging existing gestures.

Just a grammar point: the above text in read said 'should' and here you are saying 'are'. Keep consistent on tense "Helpful indicators to identify a pin would be name, contact, etc."

This is great but as a reader i'd like to see you editorialize at least one of the sketches below. How did your understanding of the user inform the layout and component choice of these screens?

Also a small thing: instead of 'feedback from user interviews' since it was exploratory research you did it would be 'insights from user interviews'.

Workflow diagrams should also help you think about how to facilitate task completion in the app with the fewest steps possible. In the case of a feature being added to an existing app, these should also help you think about where in the existing IA your will be adding this feature, updating or extending existing IA.

I think the text on these cards will look better if left aligned. The sentences are too long to be centered.

I like your insertion of this and the hierarchy you've created.

"Add a feature" is Design Lab language. Nearly all case studies outside of bootcamps are just adding an additional feature or functionality. Maybe you could just rephrase as "Adding Pinned Messages to iMessage" and then you already address 'Scope' further down under 'Scope'.

What do you mean by this? Do you mean that you clarified the core workflow of the site?

So this is a good example of the above comment I made. You mention that this method helped you identify where to focus for usability testing. So what did you identify? The project specific decisions should stand out as much or even more than these reflections on your method selection.

I really like how you're using your heading for each section to succinctly describe why you used each method and what it helped with but I think these snippets where you describe what decisions were actually made during each method should also have some prominence. I'm wondering if you could use your red text style here to code these takeaways?

I like that you've listed out these requirements here but I still think you need to show your research insights above so that it's clear what you learned from the research itself before figuring out what it might mean for your design solution.

The images below need to be much much larger. Also can you make them open in a lightbox so that readers can view the details on each screen?

Your kind of walking the reader through the steps of using the app right? If so, why not use numbers 1, 2, 3 to help communicate this?

For whom is this annual? Do you need to name your target market here?

Is this going to launch a form or an email to:

How about an About page where you can write your full blurb and include your resume link there?

I'm really loving this color palette!

Do you want to say 'Product Designer' or 'UX Designer.' I think 'designer' is a little too vague.

It's a bit odd to see this used as a title when in other parts of the case study it was used as an informational banner.

These images are looking good. Can they be enlarged upon click?

This is feeling too prominent. I wonder if you could just reduce it to one word or even an icon?

I really like how you've called attention to what you were able to solve for in this last paragraph. Since the first two bullets are about what method you used and what you hoped to gain by using it they are very different than the third bullet. Maybe you can try giving these two classes of information different visual representation. Maybe one text style can be used for information about your process and method selection and another to describe key insights and learnings!

I don't think you need to label your methods. This way your paragraphs flow one into the next and you describe what you did next and why. You can name those methods in the body text.

How does this relate to your HMW question? It's feeling a bit like you are just plopping the methods down without tying them together into a story. By distilling your research insights into a user persona you could begin ideating on that HMW question. Perhaps by switching the order in which you present the HMW question and the persona this could become clearer to the reader.

I don't think you need to label this...use the HMW question you ask in blue to help you tell the story.

These are very important for understanding the decisions you made downstream. Is there a way to call these out louder? Perhaps using a highlight color or background?

I think it would be better if you images enlarged upon click and then you could add a link immediately below to open the source file. It's a little unexpected to click on the image and be taken to the source file.

As body text, i'm finding this font too heavy/bold. Is this a bold or medium font? If it's regular you may want to consider something a little less chunky. It doesn't feel very comfortable for reading paragraphs.

The image here is quite blurry.

It's a very nice start Clara! The gradients look great, the text is working well. The page margins and padding work. Well done!

You need less space before each of the lines of text here and more space between the text and these action buttons.

Your logo looks a bit grainy. Make sure you upload with dimensions at least 2X that which it will be rendered on the screen and 72px/dpi (which is what we use for screen resolution).

I really like the blue gradient on this page!

The bolded text throughout is very helpful!

You should describe at a high level what that flow is here.

core workflow

The image below actually gets smaller when clicked. I think this needs to be broken up into multiple images.

"...in core workflows"

"...opportunity to create additional value to drive adoption and engagement for new and existing users"

You keep using 'find' but 'identify' is more accurate wouldn't you say?

"...goal is to add a handy feature into Apple Wall--a more general purpose tool--the analysis..."

"...identify which card will give them the best reward for any given purchase when they pay with a credit card"

Just making this more succinct.

This one is 'The User Problem".

"Competitive solutions that help users identify and manage cards which maximize their rewards for any given purchase".

I'm not sure how you are drawing this conclusion from the chart? What does store loyalty have to do with reward programs?

This is the "Revenue Model" the 'Opportunity" is below in yellow/orange.

"Business Drivers" is more common terminology.

Put this in quotations and bold it the first time you use it here.

The 'UX Research and UI Design' are I guess 'tags' but they look a lot like buttons which is weird because the whole card is the click target. I recommend making these look more like metadata tags than buttons.

Sorry I couldn't anchor this comment to the right spot on the page.

Try to keep all your screens the same size. These are smaller than the next set.

I feel like you should surface a bit more of those details here and then let the rest be seen via link in the test plan. You could include the main flows that you were testing and what you were testing for for each...discoverability, learnabilty etc.

It's nice to describe why you feel like these visuals express your brand attributes. What in the visual language communicates those values?

It's not a refresh if there wasn't a brand already. Wasn't this a new brand? "Branding"

Same as above here. More visual to start and overflow using carousel.

I think it would be good to include more upfront here and then let the overflow live in this carousel.

It feels like this would come before your user flow as the user flow explores how a user is successful at completing various tasks using the features that exist in the app.

I'm not sure you need to call this out separately from the user flow. It's one of the main purposes of doing a user flow. So maybe you can just indicate that the user flow helped you identify the pages you needed to design.

"Scoping MVP"

This is a great visual treatment.

So you identified ways that other apps have solved for this...so what? What did this help you decide?

"Identifying"

In the diagram above you should add a column for this app or your could circle where you see the opportunity for this app.

These are great insights and this is an effective way to communicate them!

This one is of a higher order so should be set above the others and not have an icon associated.

Try to use icons of a consistent weight and a boldness. Some here are line icons and others have fill. Try to keep that consistent. Also it would be good to get ones without attribution.

You should make it clear that you are offering solutions geared to a specific subset of the market that is looking to help long distance friends and family reconnect and stay in touch!

Somewhere you should make it clear that this is a hypothetical project.

Just testing this out!

Unlikely to be used unless we direct devs to do so; this could be an opportunity to get outside feedback on the design system.