If that's the case the UI curators should decide what are those 3 priority issues We can "jump" to these: 7. Don't panic by overwhelming issues. Discuss with colleagues or publish in a private wiki for the team or something 8. Decide what are the 3 most blocking entry barriers and show that to the team. We need to discuss the discovered issues so, together, we do something about them If is not, then experiments is what we needed On Jan 3, 2014, at 10:21 AM, Stephan Eggermont <stephan@stack.nl> wrote:

Sebastian wrote

...

Cheap idea for us:

Good idea for a bit later, and for the new parts.

We already have a number of well-known problems for new users. If we don’t eliminate them first, we’re not going to find much new issues. They will be hidden behind: - no discoverable way of creating classes & methods; - buttons in the system browser without a visible relationship to the pane they operate on; - context menus that don’t operate on the selected item but on a whole group; - menu size - modal editing - keyboard navigation of the ui There are quite some Pharo’ers teaching introductions to smalltalk. I think they are aware of these issues. A few of them are on my slides, at least. And a few I always have to explain.

Stephan