19

I know there's an accepted answer, and I usually do quite agree with Michael, but still this does bug my mind for two days. As a developer, I hated the Apple HIG It just didn't tell me what to do, how to do things in practice. The Windows Guideline was felt as "empty", but it could be that it did because it seemed, on Windows, actually noone follows them. ...


17

Example Style Guides For example style guides applicable to applications, you can leaf through with the usual platform style guides (e.g., Windows, Apple, Gnome) for the organization, issues, and topics you may want to have. Many topics in these guides are not relevant to form-oriented UIs, but most of the guidelines for controls, messages, and dialog boxes ...


16

I'm with @Michael Lai, and think they're a great tool to have in your bag for the right case. What they can help you with: Understanding the client As a UI/UX designer you often come into new environments, sometimes very complex ones. User journeys can help you understand processes that might be way out of your field of knowledge, by allowing your client to ...


15

"Wireframe deck" is not an industry wide term that refers to a specific presentation format. Your best bet would be to seek a definition from the employer, possibly giving them a few examples so as to illustrate that you've thought the problem through and are looking for clarification. Over on EnglishLanguage.SE a similar question was asked: What is a Deck, ...


10

As with many of the UX deliverables, it depends on what you believe the best way to communicate the information to your audience is. This is also a debate going around about personas and how useful they are to the design process. In my opinion, I generally try to create some sort of 'user journey' as a way of working out all the different things that a user ...


6

One of my mentors said that you will never die of a bad presentation. So relax, take your time, and practice. :) You followed a process to create the design. You identified pain points, user goals, issues with the existing design. Walk them through the highlights of that process. I find that summarizing the work gets me relaxed and makes the presentation ...


6

Is it reasonable to update the technical specification every time changes are made during the development of the project? Short answer: Yes, it's worth the time to update the specs. More context: Technical specification ≠ documentation, but often there is no documentation at all. So if changes are made during the course of long project there is no ...


5

I'd have to point you to this BBC Internet Blog post for an excellent reference. This blog post describes the technology strategy the BBC Future Media department is using to evolve from a relational content model and static publishing framework towards a fully dynamic semantic publishing (DSP) architecture. You will need to define and describe a set of ...


5

For me, the value has decreased with the popularity of customer experience, instead I find myself referring to an Experience Map if the project permits. I find the lines are blurred between User Journey and Experience Maps as they're similar models albeit the latter tends to be more visual. Adaptive path have a helpful article that explains their ...


4

One simple way to add an element of user research to this project as part of your UX porfolio is to suggest in possible next steps how you might go about doing user research to help improve the current design. While it isn't always necessary to show that you have used every tool or trick in your UX skill set, it is still important to show that you are ...


3

I think, user journey map - is a must have for every project. User journey map helps you understand not only how user moves from page to page, but how he thinks and what he feels at each point of journey. When you know what user thinks and what user feels, it is easier to understand his general behaviour, you know how to motivate him to do the action you ...


3

I have found the journey maps effective in following ways: Time spent - I normally map timings of varous user steps. This help quantify and identify possible inefficiencies Repeated task - I did a study of the Washington DC Metro Rail ticket purchase process, and I found that the user had to calculate the amount of money multiple times due to the gap ...


3

I think this could be handled by providing simple affordance. If it looks like a generic link, it will be a link. If it looks like a button, it will be a button. If you want to increase the affordance in your Mega Menu, you may want to consider: A down-pointing arrow next to each horizontal menu item or a right-pointing arrow next to a vertical menu item ...


3

I understand the question you are asking but think that it may be hard to give a generic one-size-fits-all answer. The UX workflow from company to company is so vast that what you ultimately decide to go with will require a lot of user research. On top of that, the workflow from product to product and even person to person is never the same (a real eye ...


3

For the "Lean" part of this: dividing the design documentation into: Style Guide - Always up to date Individual Designs - Not kept up to date after they have served their purpose. Wiki or Confluence is great for documentation since you can link from the designs to the Style Guide (and also in the case of using Confluence and Jira, link development tickets ...


3

I have experience of three different tools for creating style guides: Confluence The first style guide I implemented was built using Confluence. It was more a design pattern library, containing patterns and best practices for the most common UI design problems. Each pattern contained an example image, description how it works and why it should be used, and ...


3

Overseas development is often code for 'poor' development. I've found no amount of style guides will resolve those issues. But that's a different topic. As for what works, it varies wildly from team to team, project to project. As we build more complex web applications, with more complex interactions and the like, I'm finding the better path to go down is ...


3

Overall, I feel that the individual tools are more versatile. I think the more you mix into one deliverable, the harder it is to focus on the individual aspects. Like the example of HiFi wireframes that I mentioned in my comments, clients often get distracted by the wrong details. The other problem is that I feel like a storyboard falls more in line with a ...


2

Stick to individual artifacts (User Goals, Site Maps, Annotated Wireframes) and make sure they are consistent across all of them, without being redundant. The "just enough information" premise keeps your artifacts focused, and with the right amount of supporting fact.


2

The answer is Yes. The documentation should always be updated as there are changes from the client side. This will enable you to produce updated documentation in case of any dispute with the client. Also the development of feature and its testing will be more correct and precise if and only if the documentation is always correct. Outdated specification will ...


2

Based on my experience of producing a few style guides in various formats (html, wiki, pdf, doc), I found simple static HTML pages provided the most flexibility. It's usually developers who are driving creation of web style guides, because they are the primary beneficiary. Consequently, the burden of creating and maintaining one will likely fall on you ...


2

online Wiki with the spec Look into using a 'component library'. They take time to set up initially, but can streamline projects down the road. The idea is to document individual elements. For instance, you may have a design pattern for a search field. You'd describe this pattern in the component library, add some visuals, and, ideally, maybe even have some ...


2

If you're using Axure, then you already have access to publish to Axure Share. The annotations and notes are still readily available on the page and anyone can access it at any time. When you update the wires and republish, it uses the same url - so it a bit like a living document. I use this all the time and it's incredibly useful for sharing ideas/specs ...


2

Why not create a PSD of your UI elements. For example this is the UI Guide created by Teehan+Lax for the site Medium.


2

Speak their language "Wireframe deck": Presentation version of the wireframes you're building for development, tailored to an executive audience who wants to know x about the project. This is a very common term among execs and other "business types" who are familiar with the concept of designing an app or site (but aren't designers or developers). It is ...


2

From what I understand, if your role is that of a UX Designer then anything helping the developers understand the critical requirements, users and preliminary design work could be of benefit. The potential list of materials that theoretically could be provided is quite large, you wouldn't normally do all of these activities but here are some: business case ...


2

I wholly agree with Michael. A (UX) design process doesn't consist out of fixed steps. Not all project benefit from a persona or a detailed user research. You'll sometimes find these deliverables neglected after some time, so making them could be a waste. Talk about what you were able to do within the constraints. Since delivering an MVP at the end of the ...


2

The main thing to keep in mind, when you outsource a job, is to make sure that it doesn't become obvious that you had the job outsourced to an external or third party group for development. Having said this, what can you do to make sure your product, even with the fact that it was outsourced for development, looks like an original product that reflects you ...


1

I won't reiterate what the clarification of the deck means as other members have done that for you. But I also recently had to present a "deck" to a potential employer and I ended up creating a 4 page PDF (PowerPoint would also be fine) of the processes I used to get from point A to point B. I started with a defined workflow, then onto low-fidelity ...


1

"deck" is usually business jargon for "powerpoint presentation". Essentially a "deck of slides". In my experience, when someone asks for a "deck of..." it usually means "I gotta show my bosses something pretty in a meeting."


Only top voted, non community-wiki answers of a minimum length are eligible