A reliable way of ensuring quality is to deliver components including spacing guidelines. Think of a Design System, the complexity is in the way you’ve designed. Everything must be correct and should not differ to much from each other.

Using a prototyping tool to provide them with a way of clicking through the flow is pretty handy. And will provide them with the necessary context. Depending on the tool, it can also be used as a way to communicate efficiently.

Ps, keep responsiveness in mind.

What Wouter said about showing the impact is very strong, be strategic in how you communicate this to the different layers of management.

Use formula’s with real data to show the costs and gains in a realistic way, numbers always work.

Funny how no one notices that the headphone jack is missing.. doesn't seem like such a big deal eh ;D

Would like to read more about his thought process, some more in depth case studies. I really liked the flow of a case study done by Jason Yuan, the student who got rejected by Apple.

Hello Jack,

Thank you for sharing this, I have a few questions.

Why did you choose the current logo mark and what have you explored?

Why did you choose Lego to be the main source of inspiration and how do you find it fit with all the active products of Google?

Could you tell me more about your process and perhaps provide pros/cons/learnings?

What do you think of the branding of Google products as a whole, do you see possibility for improvement? How would you tackle such a big endeavour?

Thank you.

It seems to have problems with Symbols, which they are fixing as we speak. When you change a symbol and want to merge, it will show all the artboards where the symbol is placed.

It is currently based on artboards and not on objects, as far as I know.

What other plugins do you use?

In my opinion, the story should fit the user's environment/state. Is the user willing to scroll in order to understand the whole story? Does he/she have time for this, if not, can he/she re-enter the story easily?

Is the story "scannable" and understandable without reading every single word? Can the user find specific information when he/she returns?

Does it need to act as a page that the user uses to commit actions? Is it purely a page that provides information?

Many questions should be considered when deciding the length of a mobile webpage, same for desktop. It depends on many factors and understanding the state of the user. The length of a mobile website is linked to the function of that mobile website.

What we do know, is that users will scroll if the content is correct. If the story (storytelling) is worth scrolling for.

Heck, people nowadays care less about being run over by a car when they are scrolling through the mobile browser — one of the reason why an experiment with a traffic light being integrated into the sidewalk is introduced, here in the Netherlands.

Would it be an idea to provide the "Select date" field as inactive once the "Locations" have been filled in? And that when you decide to click on the "Select Date" field, and have filled it that it will show the last field that allows the user to specify the times?