Present the typography proposal with Echo

[vnys]

General objective: To complete the typography and spacing proposal by inviting different teams to an open conversation where we can collect feedback and analyze together how this new foundations would affect their product, what we can have in consideration before to finalize the work and how we can improve the proposal.

Specific objectives:

• To understand better our users needs and their projects.
• To ensure a high quality result with the typography and spacing work, where we make decisions covering potential coalitions in advance and avoid surprises.
• To create a dialogue to strengthen our current external communication and align expectations with our users by explaining them the current state of our work, our processes and also our goals by sharing our roadmap.

Outcome: A meeting where we explain:

1. Current font scenario, how Inter came to the conversation and how it could be applied also on web products.
2. From metrical alignment to optical alignment and how this affects icons and baseline grid.
3. Typography and spacing applied to their product.
4. Global or local density
5. EDS roadmap and alignment
6. Parallel project: a comparison between design systems and user experiences.

Description of the task added by Marina*

[marinalinn]

Already coordinate with Echo team and we will have a meeting on Tuesday (April 30) at 12:30 🎉

[marinalinn]

We had a meeting with Echo team today (Tuesday 30) where we presented:

1. Fonts: Inter + Equinor. We explained the current proposal for mobile apps and the reasons for it, and a potential usage on web apps letting them to analyze the case and giving us feedback about it in the next meeting.
2. Alignment: Optical alignment, Icons and Baseline grid. Explanation of current concepts to understand in order to explain the new proposal for typography and spacing.
3. Typography and spacing foundations: applied to Amplify. Showed them examples on how the proposal would look in their products and asked for feedback.
4. Density: Spacious, Comfortable and Compact. Showed them how density would look in their products and received feedback on how valuable is for them.
5. Roadmap: Expectations aligned and processes communicated by sharing our roadmap with them.
6. Final note: Comparison components between design systems. A quick update about the comparison file and future expectations for better collaboration.

We also needed from them a better introduction to what Echo offer to their users, main actions and pain points, devices where the products are available and so on.

Figma file here.

Action points:

• [ ] - Definitions for spacing and typography Container level.
• [x] - Echo team members will send us Figma files with products or views they think are relevant to test. Those will be presented on the next meeting.
• [ ] - In the next meeting we will discuss about the differences between web app and mobile for Echo.

• [ ] - Casper will share files showing differences between mobile and tablets
• [ ] - Check access to Echo following feedback from the team.
• [x] - 
Check with Digital field workers more about the equipment.
• [ ] - Book a another meeting to include Echo on the process with EDSM.

• [x] - Create a Slack channel to maintain the dialog with the team and follow up the action points (and not lose the chat information as in Teams)

[marinalinn]

Digital field workers