REMOTELY DRIVEN PROJECT
Working remotely can be quite chellenging due to numerous factors, but I regardlessly decided to go in that direction. I like to give the best from my side and to work on different and exciting Projects.
To help Clients and teams to create something really, really good that will move things forward.
I think the most important thing is a good communication and mutual trust between Clients and myself. Depending of the complexity of the project I usually like to approach to every task in planned stages using reliable Strategies and Processes. The problem is usually smaller when it's chopped in small chunks! Sure, every stage will be presented for a feedback.
I USUALLY WORK WITH THESE RETAINER MODELS:
Workflow usually starts with initial Skype meetings,
where we discuss about the project and project goals. First, I want to really understand your goals and research your business idea so I can implement and suggest best possible solutions. So don't get surprised, if
I prepare small questionaire for our first meeting. At the beginning we also discuss about Contract payments deadlines and deliverables.
For daily team communication I use your team chat channel on Slack. For task management and regular feedbacks Trello is the main tool. Team connection and collaboration tools like Figma and Zeplin can also be of precious help especially if the team is bigger.
For exporting assets to developer team or design team I use Zeplin which is very handy tool that can speed up development process. If it's about a fresh new web project I use Webflow for fast mockups and prototyping, which is also a great way for presenting the work to the team.
Everything starts by analyzing your business and clients/users needs that can be merged with initial concept and possible
At the very beginning, It is crucial to conduct research to get clear understanding of user needs in order to improve or create meaningful, easy-to-use and therefore successful digital product.
For that purpose I usually start with designing of surveys and conducting small interviews. To get know users and their needs sometimes I should have access to your forums, mailing lists, databases and other relevant information. I believe such aproach to Analysis can be of big help to get clear insight into the "audience" and their needs. Later, when I exemine results I will present you my thoughts about the improvements in the form of wireframes or sketches. In that earli stage I suggest to make itterations for A/B testing and present them. After I get an insight and truly understand user needs and your desired goals we can go forward to the next phase of the process.
STRATEGY - SITEMAPS
Strategy planning is very important part of the Design process. I usually start with Sitemaps and Site flows. Of course, planning is different for various platforms. It shows me roughly how many pages we will need and help me to connect project components with the mechanics inside the flow. I begin to think about simplest and best possible solution. I would try to cut down number of views/pages to make simplest but most understandable experience. After feedback we can go forward to the next stage.
PERSONAS AND USER JOURNEYS/TASKS
In this stage I like to experiment with different scenarios to accomplish best and easy to catch experience around certain user goals. I create various user tasks with different personas and analyze results of any user story. That's very usefull because this kind of imaginative approach to can reveal many issues. Data gathered from your website is also very handy in this process. It usually can give us value information about your customers as real persons.
Finally, I can give your project a visual shape. Using previous results and flows I start to sketch and organize elements into panels, forms and elements. I usually use some UI kit for doing that, but the final look will differ because I only need some kind of visual grid to speed up the process. In this stage I also think about Moodboards, Fonts, Icons, Colors etc.
MID FIDELITY MOCKUPS AND CLICKABLE TESTING
In my workflow, currently I use Figma and Photoshop. I can use Sketch too, but I'm yet on my beloved Windows machine:)
Same as in Sketch, Figma allows clickable prototypes. I think it's quite useful for testng, and I see it as a logical step in
the Product design process.
Still, I wouldn't call it Prototype, because I don't believe that bunch of images with minimal interactivity can show full scope of the Product complexity. But it's still unavoidable part of the Product creation, even if I use low-fidelity mockups. After Client approval we can go to the next step.
UI POLISHING & PROTOTYPE
In this step I will use all gathered experience from the previous steps, including discussed color scheme and consistent visual language. If I work on Web project I will mockup screens in Webflow and get it to life with animations and transitions. If it's about mobile project I could use some another tool to present my interaction ideas and thoughts. Recently I discovered Atomic.io that is capable to bring fluid animations to the prototype and even export an usable code for developers.
Working in Agile Team
I can adapt to your Team workflow easily. Trello and Slack are my everyday tools. For conference meetings we can use Skype or similar. Maybe, I will need some time to understand completelly your working process, but for sure I can pure myself into your Team and be responsible player