# London 2021

{% hint style="warning" %}
Event ended.&#x20;
{% endhint %}

#### For 2021, the theme is **curiosity**.

Spend your Saturday discovering the tricks and techniques used across industries to make sense of information.

Our talks this year are:

**Beyond Silos: Service Design Practices in UX Architecture**\
Poorume Yoo, BBC

**Use Design Thinking to Maximise the Value of Your MVP**\
Ioannis Nousis, Google

**From Chaotic Content to the Well-tempered Content Graph**\
Ian Piper, Tellura Semantics

**Systems Thinking in Practice**\
Bryn Ray, American Express

**Adopting CI/CD for Documentation Release**\
David Bailey, Synk

**Content is Context: Avoiding Cultural Assumptions**\
Frances Gordon, Simplicity

**Zenko Mapping**\
John Willshire, Smithery

**Tomorrow's Architects**\
Peter Morville, Semantic Studios

## **Event date**

Sat, 27 February 2021, 10.00am–4.45pm

## Location

Online, streaming via <https://vi.to/hubs/london/>

## Program/Schedule

### Conference starts

Join us on vi.to for a day of presentations and discussion.

### Beyond Silos: Service Design Practices in UX Architecture

Working in one product allows designers to build a strong understanding of a specific area. But it can also silo knowledge and encourage a product-specific mindset to develop, which makes it harder to create collaboration opportunities to find a solution together.

The BBC UX Architect (UXA) team uses a service design approach to stay curious with a holistic view beyond the silos. As a new joiner, I experienced a dynamic change of the team’s challenges, know-hows, and impact. I’ll share how service design creates new connections between products and stakeholders that brings business impact.

Presented by [Poorume Yoo](/community/poorume-yoo.md), BBC

### Use Design Thinking to Maximise the Value of Your MVP

In today’s world of tech, we spend so much time and money building MVPs and forget that we can learn what we need by faster, more effective means. Ioannis Nousis, Interaction Designer at Google discusses how we can maximise the rate of learning by minimising the time to try things and build products that have product-market fit and a lower chance of failing.

Presented by: [Ioannis Nousis](/community/ioannis-nousis.md), Google

### From Chaotic Content to the Well-tempered Content Graph

Organisations often suffer from the twin problems of how to find information and how to re-use it. Traditional approaches are increasingly inadequate as products become more complex.

I'll show how to address both of these needs by using structured content, based on a content model. Using classification and structured taxonomy, we arrive at the content graph.

Bringing order to content systems is a large step. I'll share a 5-step plan to help you get from here to there.

Presented by: [Ian Piper](/community/ian-piper.md), Tellura Semantics

### Systems Thinking in Practice

An introduction to using systems thinking to improve information architecture scaling in bureaucratic environments. The presentation includes a general introduction to system thinking, practical advice on how to apply it when designing information architecture, and guidance on using it to deliver change.

Presented by: [Bryn Ray](/community/bryn-ray.md), American Express

### Adopting CI/CD for Documentation Release

Release documentation is often written late in the development process; we think we can't start to write content until the software is stable, tested and ready for release. But that's the worst time to access SMEs, do the research, and write good-quality content, as we create content in a rush, or release it late. It’s a lose-lose scenario for both writers and reader**s.**

If we look at code development, we see that Continuous Integration (CI) and Continuous Delivery (CD) practices solve a similar problem. David will describe how he is adopting a CI/CD solution for documentation management, by "shifting down" to turn everyone into writers, and by "shifting left" to write documentation earlier.

Presented by: [David Bailey](/community/david-bailey.md), Synk

### Content is Context: Avoiding Cultural Assumptions

Simplification is good, but does the simple approach introduce bias? Let's look at 3 common cognitive biases and how they can affect getting the right content to the right people at the right time. We'll look at how other cultures receive and consume information to ask - how do we conceptualise content for the world of tomorrow?

Presented by: Frances Gordon, Simplicity

### Zenko Mapping

A strategic planning framework for the rest of us. Where time flies like an arrow through the double diamond, Zenko Mapping respects that impactful projects don’t always move in a straight line.

Inspired by Japanese folklore and Steward Brand’s pace layering ideas, John Willshire has developed a practical model for organising people and spaces as learning develops from sketch to scaffold to structure. Whether you’re wrestling with information, product or organisational challenges, this method helps you make progress visible, spotlight issues ahead and make sure you’re always doing the next right thing.&#x20;

Presented by: [John Willshire](/community/john-willshire.md), Smithery

### Tomorrow's Architects

We think we’re creating products, services, and software. But we’re not. We are agents of change. Our systems shape belief and behaviour at scale. Experience isn’t enough. Methods, metrics, culture, and governance are shifting. To realise the future, we must get better at planning.

In this spirited talk about the design of paths and goals, Peter Morville builds upon his famous “polar bear book” to reframe vision, strategy, process, and the information architecture of time; and draws from his latest book *Planning for Everything* to reveal four principles and six practices essential for shaping the future.

Presented by: [Peter Morville](/community/peter-morville.md), Semantic Studios

***

## Speakers

<table data-column-title-hidden data-view="cards"><thead><tr><th>Speaker</th><th>Affiliation</th><th data-hidden>Talk title</th><th data-hidden data-card-cover data-type="files">Profile pic</th></tr></thead><tbody><tr><td><a data-mention href="/pages/SOaXgoccaXr3awllZa5W">/pages/SOaXgoccaXr3awllZa5W</a></td><td>BBC</td><td><strong>Beyond Silos: Service Design Practices in UX Architecture</strong></td><td><a href="/files/MzKyJB9NgbLm0qMSry6Z">/files/MzKyJB9NgbLm0qMSry6Z</a></td></tr><tr><td><a data-mention href="/pages/8AlQRgZ9WrbeLySbes2O">/pages/8AlQRgZ9WrbeLySbes2O</a></td><td>Google</td><td><strong>Use Design Thinking to Maximise the Value of Your MVP</strong></td><td><a href="/files/naGJemeGcNzhN9dQ1D3C">/files/naGJemeGcNzhN9dQ1D3C</a></td></tr><tr><td><a data-mention href="/pages/4nrqw8KEhzkBkQI9o4Wd">/pages/4nrqw8KEhzkBkQI9o4Wd</a></td><td>Tellura Semantics</td><td><strong>From Chaotic Content to the Well-tempered Content Graph</strong></td><td><a href="/files/WQ2gXhgUP7oCY5Ef8JkQ">/files/WQ2gXhgUP7oCY5Ef8JkQ</a></td></tr><tr><td><a data-mention href="/pages/a0xgF3IAnHkIXsX9Dft4">/pages/a0xgF3IAnHkIXsX9Dft4</a></td><td>American Express</td><td><strong>Systems Thinking in Practice</strong></td><td><a href="/files/TkQVrTphhVJCazg1WwwG">/files/TkQVrTphhVJCazg1WwwG</a></td></tr><tr><td><a data-mention href="/pages/WrBzWcItxLxvqu5qkxte">/pages/WrBzWcItxLxvqu5qkxte</a></td><td>Synk</td><td><strong>Adopting CI/CD for Documentation Release</strong></td><td><a href="/files/ldr8uSdkoP1t4a2iOC5z">/files/ldr8uSdkoP1t4a2iOC5z</a></td></tr><tr><td><a data-mention href="/pages/IQUAc2dEmAW2tZlz6eEp">/pages/IQUAc2dEmAW2tZlz6eEp</a></td><td>Simplicity</td><td><strong>Content is Context: Avoiding Cultural Assumptions</strong></td><td><a href="/files/dQcU4zD70xDpT7AyitGQ">/files/dQcU4zD70xDpT7AyitGQ</a></td></tr><tr><td><a data-mention href="/pages/LMsPzN9bASYHIvAt0HbC">/pages/LMsPzN9bASYHIvAt0HbC</a></td><td>Smithery</td><td><strong>Zenko Mapping</strong></td><td><a href="/files/W9OZDTbEyiYmSLJ5rIQX">/files/W9OZDTbEyiYmSLJ5rIQX</a></td></tr><tr><td><a data-mention href="/pages/85EVBYAtybY5owdccFg9">/pages/85EVBYAtybY5owdccFg9</a></td><td>Semantic Studios</td><td><strong>Tomorrow's Architects</strong></td><td><a href="/files/eMt4Hwv71vYTkE58LIyA">/files/eMt4Hwv71vYTkE58LIyA</a></td></tr></tbody></table>

***

## Team

<table data-card-size="large" data-column-title-hidden data-view="cards"><thead><tr><th>Name</th><th data-hidden data-card-cover data-type="files">Profile</th></tr></thead><tbody><tr><td><a data-mention href="/pages/7vNocNL45hZDBSFzPWgd">/pages/7vNocNL45hZDBSFzPWgd</a></td><td><a href="/files/Rk6qbtAH0xtBTAY6SJdJ">/files/Rk6qbtAH0xtBTAY6SJdJ</a></td></tr><tr><td><a data-mention href="/pages/khlt2PvKeZlW7iRN9rg7">/pages/khlt2PvKeZlW7iRN9rg7</a></td><td><a href="/files/nsFxq5e4E2dHLFKHQDBw">/files/nsFxq5e4E2dHLFKHQDBw</a></td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://london.worldiaday.org/events/london-2021.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
