Answer the question
In order to leave comments, you need to log in
How to draw up the right TOR for a designer / layout designer?
Actually a subject.
I myself am a programmer and I'm used to somewhat different TK. Now we need to hire people for the project and I don’t want to torment them with all sorts of clarifications and additions.
How to state what kind of design I want? Do I need to give examples? Should I sketch a layout/sketch?
What design points need to be clarified? Example: That button onhover should be a different color.
If possible, please provide a link to a properly formatted/composed ToR.
What does a layout designer need to know?
Should he be doing some template work or is he just translating psd to (x)html?
UPD 1: Interested in both design and implementation.
Z.Y. I'll update this thread as more questions come up...
Answer the question
In order to leave comments, you need to log in
The fact that you raised this issue is already good.
In my opinion, one should not recommend to the designer what he needs to do. And a competent designer / layout designer himself should draw up such a brief or terms of reference that will help him in his work better than your recommendations. Isn't that his/her job?
The prototype should convey the idea of the project, but should not contain the design. But a prototype is needed. How do you understand what you want from a designer so that he shoves the unimpressible onto the page, and the designer to understand what and where to insert. And preferably, if you want to place text on the page, then write not “some text”, but not be lazy, type a piece of text, of medium (or even maximum) length. This also applies to nicknames and other similar inscriptions, otherwise you will think about what to do with nicknames later. the nickname wwwwww doesn't fit, but the nickname iiiiiiii fits into the design, albeit longer.
It would be nice to start by understanding - do you mean exactly the designer, or the Photoshop layout designer? Design is, as it were, not only drawing pictures, but, first of all, designing an interface and user interaction with it, where pictures are needed only for visual accents on interface elements.
So if you set a task for the designer, you should define the goals of the interface and user stories with characters, but not the implementation details.
And if the task is assigned to a person who has not heard about interaction design, then apparently this part of the work has already been done in one way or another, and then the technical specifications should reflect the technical details (requirements for layout, validation, browsers, etc). It is understandable to provide the photoshopper with page / screen thumbnails (or better, a working prototype with block markings).
Something like this…
Describe in detail what you need (examples can only spoil the initial ideas of the designer), do not be too lazy to draw wireframes (prototypes) on all pages.
Example: That button onhover should be a different color.
in principle, the technical specifications for the content for different IT industries do not differ much.
you don’t get technical specifications in the form of a set of cubes that need to be assembled correctly and the customer will pat you on the head?
so here, you need to indicate the direction in which the whole caravan will move. along the way, of course, there will be a moment when you don’t like what you see (this happens often with us), just say so.
everything is simple with the layout designer, he semi-mechanically transfers data from the layout to the layout. just don’t tell him about it - he will be very offended)))
it’s important for him that the entire interface works and looks the same in all (in most versions of browsers)
you need to discuss with him how you will punish users with old browsers, well, or his compensation for his spent nerves.
it often happens when a designer is not completely versed in the layout of site layouts, he makes a crazy design because of which the layout designer then suffers, so it’s best to hire a generalist who will draw and open it. or again prepare money for the layout designer's nerves...
by layout designer I mean a bunch of layout designer and javascripter.
in general, there are no ideal technical specifications and it is necessary to discuss the situation in advance so that in the process they can control the process and none of the hired employees experience discomfort
From my experience, the best thing is to find a good designer, work closely and closely with him for a year or two (even without technical specifications, but constantly discussing ideas and vision). After that, the need for TK disappears as such, and if you get along well, the “contact” will be quite close even at the stage of ideas.
A good team is worth a lot.
> What design points need to be clarified?
Time after time, the designers and layout designers I've worked with forget to specify how the page should stretch when resizing.
> What does a coder need to know?
Should he be doing some template work or is he just translating psd to (x)html?
The layout designer needs a psd-picture and information about what is not visible on it (how the site stretches, where are the hovers). That's enough. It seems to me that the initial template is the programmer's concern.
You, as a design customer, must answer the question “ What? ". Those. that there is a list of news (title, date, picture, short description), give 5 typical news. Give content - this greatly simplifies the creation of design.
The designer must answer the question “ How? » - how he will issue the output of this very list of news. And you don’t have to do his work for the designer (tell him what color / shade buttons, fonts, dies, etc. should be) - he will pout and communications with him will be ruined.
Of course, you can first discuss the desired introductory together:
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question