When working on a new project, I firmly believe Design Sprints are one of the best ways to generate and validate new ideas. I’ve done loads of them now, and I always jump at the chance to run one (even remotely).
The process is collaborative and structured,
Quick and customer focussed,
Inspiring and insightful.
Perfect? Well… Here’s what happened to us recently.
It’s Wednesday. We’re halfway through a Sprint, and things don’t look great: The client is already worried that we wasted too much time on Monday’s unpacking session reviewing insights they already had. Then after presenting them a design…
Start: 04:23am Fri 11th August
Finish: 17:56 Sat 12th August
My Grandad said to me when I was a young lad, “you’re blessed with a body that will do anything that you tell it to”.
And Those words have stuck with me. Ever since hearing them, I’ve done my best to see how far I can push myself.
I’ll try and be brief with the backstory. If you’re interested in my past cycling experience, then check out the training archives. The National Hill Climb (failure) is a good place to start — it’s the reason I started this…
Design principles — An excellent reference for designers to ensure their work aligns with the product, company, or team vision. For anyone unfamiliar, the digital services page on GOV.UK is a great example of them in action.
Last year the Nordnet Design Studio came up with some of our own. We ran a day long workshop, and through series of fun exercises, we captured the vision and personality of Nordnet in four short statements.
Designs Sprints are awesome. At Nordnet, we run them to kick off almost every new product we create.
When we need to bring an idea to life, we Sprint. Our Head of Product Design, Marcus Castenfors has already talked about how we run co-located Sprints in a great article called Design is a team sport. If you aren’t already familiar with how Sprints work, or need a refresher I highly recommend popping the kettle on and reading that first. Actually, no, I’ll pop the kettle on and take five whilst you catch up.
The Nordnet design team are huge fans of Atomic Design. We use it to create and organise our UI Kit, used daily by our designers and marketing department to create consistent content and products. Fast.
As our UI Kit evolves, we’re constantly trying to develop our workflow and process too. Since we last looked at the Nordnet UI Kit on Medium, the layout and structure have seen a complete redesign. Every Atom, Molecule, Template, or Page (collectively I’ll call them components) is now well documented and organised.
More designers than ever now help contribute, so we need a robust way…
I’d like to be a better writer.
A lot of people who say “I‘d like to be good at XYZ”, rarely mean it. What they mean to say is “I like the idea of being good at XYZ”.
There’s a huge difference. And I’m as guilty as anyone.
I’d like to be a better writer.
I also want a little vegetable garden and maybe some chickens. That’s because I love cooking, using fresh ingredients, and eggs.
But chickens are messy. And I don’t enjoy gardening.
Still, I find myself saying “Oh, I’d love a little vegetable garden of my own…
We’ve already talked about our Atomic Workflow and the products and tools we use to keep the team in sync. But what’s it like working this way on a day-to-day basis? Is it time consuming? How do we decide when to create a new Atom or Molecule? Or document changes and suggestions to existing assets?
We’d like to share our current process in the Nordnet design studio. We’re interested to hear about other companies’ workflows too. Especially across distributed teams.
Atomic thinking can be applied to almost anything, but I’d like to use our UI Kit sketch file as an…
Thanks to our Atomic Workflow we have a solid design system in place at Nordnet. The jewel in the crown being a Sketch file that contains our UI Kit. Hundreds of design assets inside. Everything from typography guidelines and input states, to grids and colour pallets. And to top it off, it’s meticulously organised into reusable symbols and text styles. Delicious!
The challenge is making sure our designers always have the latest version of the UI Kit at their disposal. Without creating any overhead to them. …
We’ve recently introduced Atomic Design to manage our digital assets and workflow, increase speed, and maintain consistency across our product offering.
In this article we’ll give an overview of the Atomic way of thinking, and share how we’ve applied it — with a little help from BEM and Git.
If you’re already familiar with the concept, you might want to skip this part. Grab a coffee and we’ll meet you at “Creating an Atomic UI kit”.
Atomic Design is a methodology used to construct design systems. The concept was first coined by Brad Frost in 2013. …
I'm @rmalpass. An award winning digital designer living in North West England and working with Ombori in beautiful Stockholm.