Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

Hi Sabin

Thanks for the offer of your help.

I think others are fairly busy so we might be able to work on this together.

Because you've come on board after I've sent a few emails earlier on, I have inserted the text of some of these below.

I sent this 26th  May;
If possible, I'd like to see a degree of formalisation of how the design team will work together with suggestions of stages for taking an idea and transforming it into a form that we have agreement on for submission to the pool of programmers.

This is about building relationships between the design team members but also between the design team and programmers so they feel part of the design team.

It's like selling ideas to management - well articulated ideas with supporting evidence should make a difference in getting done what the Design Team thinks by consensus is necessary to improve the product.

Here are some suggestions for stages;

1) Someone comes up with an idea
2) Idea is posted on Design/WhiteBoards and emailed to team members
3) Idea is discussed and debated with ample opportunity to test idea and gather arguments for and against 4) Goes to vote stage by design members after member proposes that they do this - if passed goes to Stage 5) 5) A Design/Whiteboards paper for the idea if constructed giving a formalised breakdown of the idea - i.e. Overview, Introduction, Main Body with evidence, conclusions (why idea is a good one) and references/bibliography.
6) Submitted to programmers pool for their feedback.
7) Followup

We need to make this reasonably professional without turning it into a Phd. It makes it transparent for all.

I know that some of these things are already done, but using a system will make it more likely that progress is seen to be made on some very interesting and beneficial ideas.

Sent 6th June

I'm looking for about a total of 3-5 members for this sub-team. I would expect that this small project will take 2-3 weeks. We can use the knowledge and experience of others to get feedback on our proposals as we suggest them so we don't overlook useful ideas and suggestions.

I suggest that we create a tag specifically for this project i.e. [DTF] standing for Design Team Formalisation or maybe someone can come up with a more apt one.

So for those that want to get involved in this, let me know and we'll aim to get started in the next week. We can put together a simple outline which will expand where necessary on the obvious initial steps of ;

1) Set the general brief for the project in clear, unambiguous language
2) Summarise previous work and suggestions
3) Discuss and design the structure
4) Get feedback
5) Changes as required (repeat 4 and 5 as necessary)
6) Plan for implementation
7) Implement

We can then try this out on real things to do and monitor how well the structure works and what tweaks are required.

These give a fairly good overview of what I believe we need to achieve. Would you like to think over these and add any further comments or suggestions?

We've got all these great ideas coming from all directions with no traffic controller in place - a traffic jam of ideas without a road network to follow to get the correct destination.



On 6/11/2011 1:21 PM, Sabin Densmore wrote:
See my notes below, and thanks for the welcome.

On 6/10/2011 5:59 PM, Phil Jackson wrote:
Hi Sabin

We're at a stage where we are getting a lot of good ideas but needing to formalise procedures so everyone can see how things are done.

I'm wanting to get a few of the design team members coordinated on this project and you are welcome to join me if you are interested.
I'm in. Let me know how I can help.

if not, look at all the emails and get involved discussing ideas and also look at the DesignTeam/Whiteboards to see what is there already.
Looking through those now. I like the zeitgeist of the ideas, for sure: save space, provide tip-of-cursor access to appropriate functions. Good stuff all around.

You can add any original ideas of improved ones to your own Whiteboard page and then link it back to the main whiteboards paper.


Phil Jackson

On 6/11/2011 2:23 AM, Sabin Densmore wrote:
Hello all.

I'm not sure what the "hey I'm new here" protocol is, so I figured I
would risk it and introduce myself.

I've used OpenOffice since the early days, and am glad to see
LibreOffice continue strongly forward. I figured that since I've gotten
so much from the good work that maybe I should give back what I can.

The ideas I've seen floating around for side tabs and panels and new
interactions are all really striking and I'm excited to see stuff come
to fruition.

Basically, I guess what I want to say is "hey there" and "how can I
help?" I have experience in user interface/interaction design and
presentation, user testing, Agile project management. I work fulltime as
an Information Architect/UX Designer for a financial services firm in
Boston, MA. I've been there for five years and have been doing this kind
of work for 10.

Should I jump in? Is there a list of things to tackle? Let me know how I
can help.
- sabin

Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.