Nice post, David. I recently updated my website trying to go towards the direction you mentioned and I noticed I'm not used to record much of the process. I should start taking more pictures of board sketches, drafts on paper, meetings and all those things involved in the process so it could serve as visuals for portfolio projects.
On another note, how often do you see a unicorn type of portfolio? I ask you that because it seems I'm walking towards this crazy magic land. I'm far from being a specialist in UI, UX and Development, but I'm definitely a multipotentialite. I started as a UI Designer with some frontend development knowledge then I became a UX Designer. But, due to lack of team members and also due to the fact that people knew I could create UIs, I always kept some UI responsibilities. For a while now, I found myself doing more and more frontend work to implement the ideas usually because the projects I'm involved don't have a specific frontend developer and the backend guys struggle with frontend.
Recently, I started learning more and more about backend so my frontend work could be done faster. But now I find myself studying everything and experiencing the "Jack of all trades, master of none" complex. The problem is: I kind of like it. I definitely prefer to work on a team with specialists on each area which I can count on, so I can focus only on UX. But this doesn't happen often. And when it does, it's good that I have a broad knowledge so I can serve as a bridge between designers and developers.
My questions to you: Based on your experience in different companies and different teams, do you think there is value in having a UX unicorn (if I can call it that) in the team? Does it facilitate discussions and gaps between ideas and implementation? Would you hire one or would you give priority only to specialists?