I'm trying to figure out the best way to present just two links on a page. This page appears after login and redirects users to the selected page. Do you have any suggestion for this type of page?
closed as primarily opinion-based by Mayo, Devin, SteveD, msanford, maxathousand Jan 18 '17 at 20:39
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
In general, I like PhillipW's idea of providing two buttons on the log-in page, but due to the name "Dashboard", I would recommend always taking users there first as a landing page (that's what's communicated in my mind by a "Dashboard"). There can be a large, easy to find button that takes them to the Report System from the Dashboard. Also, there could be a user preference or setting for advanced users that customizes what their default page is if they would prefer automatically going to Report System instead Dashboard.
I think you should use a background image that makes the buttons more visible or you can try something more creative like split the screen into two sections, each with a screenshot of the page mentioned in the buttons (dashboard/ report system) and the correspondent button.
This simple page, with a lot of white space, reminds me of an empty state and I think you could find inspiration on Material Design Guidelines:
Displaying empty states
The most basic empty state displays a non-interactive image and a text tagline.
Use an image that:
Is subtle and neutral with respect to the background Conveys the purpose and potential of the app in a lively way, such as your app's icon Include a tagline that:
Has a positive tone Is consistent with your brand Conveys the purpose of the app without appearing to be actionable
With this small amount of information I would suggest to take the user to the dashboard first, as J. Dimeo did.
You could try to find out, what your users need. Think about the task users want to achieve with your application. Is the dashboard clearly used more often or the report system? Maybe you could create a diagram like this (source: http://userfocus.co.uk/articles/prioritising-functions.html) and find it out.
As seen in the comment from Martyn, if thought about new users, the way to the dashboard would be most likely the best. But what do advanced users or power users want?
Maybe You can ask your users, what they want or test it with a prototype.
From a Information Architecture point of view would it not make sense to have Dashboard shown first on login and then a "Switch to Reporting" button prominently on the page?
Blue generally means something that's official about now, green is something we think of as go. And since I'm assuming reports is the purpose of this... and due to our trained use of options and values of relevance to current knowledge being top right, and our expectation of identification, furtherance and purpose being bottom right, these two buttons should be like this: