Not all button groups needs a primary button. Sometimes all actions are equally desirable. Button themes need to accurately reflect the content (i.e. action).
The following captures the Skype discussion.
[3/25/14, 4:49:13 PM] Erik Rath: I'm working on the analysis and design for the Approve Proposal user story. I was taking a look at how to present the Approve/Reject buttons on the Proposal Review pages (which is where an approver would do the approving/rejecting). I am thinking that this may be a good situation for using green (approve) and red (reject) buttons. I think the fact that the user's primary actions are conflicting, binary actions, then using color to help communicate that relationship, and make it very clear which is which, would be a valuable cue for users. What do you guys think?
[3/25/14, 4:51:42 PM] Tara Noelle Bazler: sounds fine to me in this case
[3/25/14, 4:52:24 PM] Chris Basham: We concur.
[3/25/14, 4:53:50 PM] Chris Basham: Reject ~ Red ~ Danger. Approve ~ Green ~ Success.
[3/25/14, 4:55:10 PM] Erik Rath: Cool. I will move ahead with the design and will add some notes in the discussion docs capturing the reasoning.
Not all button groups needs a primary button. Sometimes all actions are equally desirable. Button themes need to accurately reflect the content (i.e. action).
The following captures the Skype discussion.