This is a draft.
Our team is currently cracking away at creating more content to make our Handbook something increggdible. Soon, you'll be able to explore it fully. In the meantime, think of it as a carton of eggs, each section packed with the potential to deliver something eggceptional.
Design Iterations
To iterate or not to iterate, that is not the question. The question is how! How to iterate.
The act of sharing your work is like a moment of eclosion. A solemn occasion when you let your baby go! A special one. Which makes your heart kind of flutter, like a butterfly in a cocoon. If you don’t feel as strongly, perhaps something isn’t quite right.
You get the point. In other words, sharing your work is extraordinarily important. What's the point of putting your effort down, day in and day, out if you'd wrap it all up with a lousy iteration? Right?
But we iterate a lot, you may argue. Do I have to be that pompous and thorough every time, you may ask. Yes. Yes, you most certainly do.
That is respecting your own work, your own effort. That is valuing your work and the work of others working alongside you. Keep that in mind.
Structure of the iteration.
The iteration should be clear about its goals. Why are we sharing this now? What is the purpose? What do we expect in return? Feedback, always.
It should also allow the recipient to clearly identify the deliverables and provide direct feedback.
Privileged numbered lists. Easier to read. Simpler to reply to. More straightforward to refer to when providing comments.
In addition, every iteration should answer 3 basic questions:
What? What has been done?
Why? Why has it been done/decided in a given manner?
How? How was it accomplished?
Some things, we hope, go without saying: keep it professional, cordial, and warm, especially on the cold winter days.
An example.
But an example only. Don't keep any of the demonstrative text. Delete the whole thing and rewrite it using your own, naturally-poetic phrasing. Liberate the Shakespeare in you. Change the structure if you see fit, but save the above-mentioned rant in your cerebral hard drive.
It goes like this:
Hello @client!
Goals of this iteration.
Delete the title. Or change it. Or keep it. Whatever.
After our last discussion, we took the time to iterate on the wireframes. Your feedback has been received, we worked on it, and we are ready to share an updated version. As always, we'll be looking forward to your feedback. Feel free to do so here in Notion or directly on the Figma file. As you prefer.
What is being shared in this iteration
Again, title: chop it off or change it. Or keep it. Whatever.
Over the last few days, as you'd probably expect, we've been reworking the Home and Product pages.
Having this in mind, there are a few extra notes we'd like you to be aware of:
1. As with any page of this website, both Home and Product pages are meant to be built -n blocks. This way, we aim to achieve full modularity and scalability, meaning blocks may be interchangeably used across any page.
2. Keep in mind that there are absolutely no visual concerns in this iteration: this is mostly about content, structure, and architecture.
Onwards with the actual deliverables, below.
Below, create a detailed breakdown of all the deliverables or any particular points that require dedicated attention or feedback. Remember, your decisions must have had logical reasoning.
We hope. Make sure those are clear as water.
Homepage
Here, if needed, you may include a brief description of the works endured on the Homepage and what has been done.
Looking at the analytics, the Homepage is the main entry point of the website. Almost, 98%. Naturally, it is the core starting point in any conversion funnel. As a result, we took some extra time to design a more immersive experience, strategise its structure, and plan a better conversion flow. If there's a place that will impact the conversion rates, it is the homepage.
This is also when you focus on the Why and the How by referring to the What. Confusing? It will be clear below.
Using a numbered list, you should list all the worth-noting decisions taken, the deliverables, and the ones that require attention. Each of the entries should be appropriately justified, having the rationale behind them accurately reasoned.
1. What this is (What). How it was accomplished (How). Why it has been done like this (Why).
2. We opted to do X, Y, and Z (What). Aware of this assumption, we believe that having a more fluid layout will increase conversion (How) because of A, B, and C (Why).
3. Another deliverable. Another What, How, and Why. You can find the Figma link right here. The prototype is fully clickable, so you can navigate things around.
[Figma Link]
Product page
The same principle applies here. Add a description, list things, and reason them. Straightforward.
Clickable prototype
Should a dedicated clickable prototype, video, or other exist, you can share them here.
We've also taken the time to create a fully interactable prototype for a more immersive experience. We thought this to be the best way to showcase the whole website immersion.
Here's the link: [Figma Link]
With no further ado, thank you very much for taking the time. We're really looking forward to getting your feedback and improving from here.
As always, once you're feedback is collected and consolidated, we are happy to schedule a call and discuss things in more detail.
The Significa Team.
Done. It seems a bit long, but your awesome work deserves a matching presentation.