Thousands of designers struggle to join the development teams and departments and search for clues of how they can navigate their day-to-day product design delivery. buff.ly/2nALF3r

Look at the clues; for a brief moment, try to be a Sherlock Holmes. Try to find anything that is design-related, including anything the design has written on it, whether it’s an epic, story, task, or even the label on the left-hand side. buff.ly/phtHoIp

I know we designers can not help it! If this is your first design development intervention or you are arriving at a new development team, instead of throwing a bunch of opinions and broadcasting your misunderstanding of the current environment – buff.ly/k8UNthe

After usually 3 to 5 sprints, you realise how your team operates with the main design challenges you might have. If you settle in Jira, you will have enough evidence to put together a short yet very powerful presentation on product design delivery – buff.ly/n0CTNDi

The opportunity to be prepared for every single retrospective, usually happening biweekly, where you can clearly articulate and often debate what we can improve in terms of the design delivery – buff.ly/u0rrNj0

This article will take a more practical approach to product design delivery in complex development environments. buff.ly/e9IzkC9

Sprint planning is no different from development spring planning. However, we tend to differ in what we discuss in the context of existing and new components in a design system. buff.ly/NPyoka5

You would not need a refinement session unless you are in a team of 40+ designers serving 600+ developers. It’s a simple alignment across the organisation as to why the dependencies on specific features and behaviours play a vital role in the success – buff.ly/Q3mvi6R

It’s commonly understood that well-defined routines can be a pivotal point in an organisation’s success. One hundred, if not thousands, managers organise the time through planning and various frameworks, yet we all still end up extremely busy – buff.ly/wJxQFsz

Stand-ups have become an organisational acronym for time-wasting. Why is it that so many teams use it for discussing problems and challenges instead of one-minute updates? buff.ly/evUSZKT

The end of the sprint is often marked as a delivery gate where the feature is built, tested and deployed, and in some cases even integrated. In terms of the “design delivery” and “design sprint” – buff.ly/YGg2izr

Therefore, we have created so-called tokens of trust. These little artefacts are part of our Figma space that signposts the co-existence between user research, user experience, user interface and the knowledgebase. buff.ly/eSEpCwY

This article will look at the practical implementation of our previous Product Design Planning. Before we dive into the details and changes between protecting and broadcasting – buff.ly/HRkRLCA

Thousands of tutorials fly through YouTube, Instagram, and LinkedIn, fooling the design community into thinking that being a better resource to the existing or newly established design team is the only way to serve the organisation – buff.ly/0eN2IaL

In order to achieve change within the complex development environment, you need knowledge, let alone a knowledge-based space that you can refer to as a common ground for all your subsequent decisions – buff.ly/M3NTUWQ

We organise the logic clusters that reflect the organisation structure, allowing all members of the team to find the specific lens on topics like content model, content strategy, content structure, IA, mental model, behavioural model – buff.ly/oER0Y6J

Over the years, Confluence has become cluttered with PowerPoint presentations lacking a naming convention, making it harder to manage our product development records – buff.ly/yPRineB

Instead of going back and forth and communicating over a variety of channels where the presentation is, we can now have the defined task source and presentation — one click away. Hustle-free collaboration with all comments clearly marked in one place – buff.ly/LGuxtbN

If we document our research in confluence, we can link to a specific task. That way, our team will see the effort (Story points) and be directly linked to the impact(↘︎Link) that it could make – buff.ly/Kt7hpc4

In the same way, we have defined 3x3 knowledgebase in Confluence the same way we define task environment in Jira. Look at it as two sides of the same coin — once referring to a source and the other broadcast – buff.ly/iRzHnBH