Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cWOip-0000Gv-CH for pgadmin-hackers@arkaria.postgresql.org; Wed, 25 Jan 2017 14:38:51 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cWOio-0001YD-Va for pgadmin-hackers@arkaria.postgresql.org; Wed, 25 Jan 2017 14:38:51 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cWOiZ-00015b-JQ for pgadmin-hackers@postgresql.org; Wed, 25 Jan 2017 14:38:35 +0000 Received: from mail-it0-x231.google.com ([2607:f8b0:4001:c0b::231]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1cWOiW-0001jk-5N for pgadmin-hackers@postgresql.org; Wed, 25 Jan 2017 14:38:34 +0000 Received: by mail-it0-x231.google.com with SMTP id r185so13415333ita.0 for ; Wed, 25 Jan 2017 06:38:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pivotal-io.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=StAF1JmDRhrM43Rh32EN4tvkT3CaurLvhrgzRg1rWFY=; b=P0PVru367iRlwULQOV85M/dLyqFEM790HXgW6BOkXNfKMXdNJDQpIevmRAk8yH9Y3V AZGjjtdjxLBuimGqoG5MDbyz1XMdN+SwJYjrPHU4442COIWeol1WoEI3SHkog3tR4ucb JDK2ETRhVuvqzBtSV61X4WcgDyiPfjH+XlqFgekd7RBEYkoYulIVkIzSG3yTRm5TsHB3 VmEua1sxW2483RaMXnoUu3muQ3+WClkDzasLZJWwk4rRGiplHwD6yJ312QYRvQTfPpm+ ilDLQhw0/UTlQt2xjwkCG5/Uhh3950v272WgUt65q4c3Hd0OcGYiXu69Dn9UXXYcLw3G /l9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=StAF1JmDRhrM43Rh32EN4tvkT3CaurLvhrgzRg1rWFY=; b=f1+kvmS/jGZ8ZxOfnARrlxTEnxK1aMtz288NE5t+gwsnHOUd0NTI5ndDTc/aga6eY6 BUpeJQgXSIHm1oVIjj87RbOQS7WbX5NSrVnlCknuiZ1N//cZeimZ6oxUde2UOdihevu5 53t6HFaivscmNK11WJobVs1Z9Otx6mQ7JEuRQ7yIG0acgBAK73YXA0g7PRRMbZmjs1/E hi70Bdoy7S1VqQbXr2dNm3xRY5Dr/mvnCSe/M9AvYuGaBxhxvo5G6tViyK4hTjqYfxKO Bxq0LTw2mzAqsI73zKlmBY29Zbpn3Q1RkxSwzgTvXzYUkoYoObpW1HwQyhKK6ZDrnhiG aELQ== X-Gm-Message-State: AIkVDXILUhlPmL4/tbQe6sGe9y162MPXTOKOj5GOV9TJh1BK5VnLS8/qGV6PaCNiWZz7JsTgYAwuv+5gnIdOIxu/ X-Received: by 10.36.40.142 with SMTP id h136mr3289503ith.95.1485355109457; Wed, 25 Jan 2017 06:38:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.79.156.67 with HTTP; Wed, 25 Jan 2017 06:38:29 -0800 (PST) In-Reply-To: References: From: Raffi Holzer Date: Wed, 25 Jan 2017 09:38:29 -0500 Message-ID: Subject: Re: User Research Findings into PgAdmin To: Dave Page Cc: pgadmin-hackers , Shirley Wang , Robert Eckhardt , Edgar Gonzalez Content-Type: multipart/alternative; boundary=001a113f67fcaa709c0546ec2f4e X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgadmin-hackers Precedence: bulk Sender: pgadmin-hackers-owner@postgresql.org --001a113f67fcaa709c0546ec2f4e Content-Type: text/plain; charset=UTF-8 Hi Dave, We can definitely send a summary via email. Just to clarify those points you brought up. Syntax highlighting definitely does exist and is totally discoverable but people still seemed to miss it. Our best guess as to why so many users miss it is because of the relatively small contrast in colors (Navy vs black). Regarding autocomplete, despite it being documented, almost none of the long time customers we spoke with knew it existed which suggests they're not reading the documentation very closely or at all. Regarding the comments you mentioned, the one regarding column names was talking about preserving the column name when moving data to Excel. And I'll admit, the other comment is pretty unclear out of context. We probably should not have included it as is. A summary of the findings will be forthcoming. On Wed, Jan 25, 2017 at 4:25 AM, Dave Page wrote: > Hi > > On Tue, Jan 24, 2017 at 9:42 PM, Raffi Holzer wrote: > > Hi, > > As part of a project to enable pgAdmin4 to work with Greenplum > databases, > > we conducted user research into pgAdmin. We wanted to share those > insights > > and potentially develop against them but first wanted to get feedback > from > > the pgAdmin group. To that end we created the video below that summarizes > > our findings. Let us know what you think. > > > > https://youtu.be/BylcblYw8sU > > That's very helpful, thank you. Can you please summarise your findings > in an email to the list so we can work with it within our normal > process? > > I will note that whilst I agree some of the points raised need further > work in pgAdmin 4, some of them make little sense - most notably > Syntax Highlighting which we've had for ~17 years, and works > automatically, thus not requiring any kind of user discovery beyond > typing some SQL into the query tool. Auto-complete is another example > of a feature we've had for years, that is documented. I agree though > that there is scope for better discovery mechanisms there. > > Some of the other comments highlighted made little to no sense to me, > for example the comment on column names @ ~3:03 and the comment on the > bottom left @ ~3:22 (this is a great example of why email is better > than a video :-) ). > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company > -- Raffi Holzer Product Manager Pivotal Labs --001a113f67fcaa709c0546ec2f4e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Dave,=C2=A0
=C2=A0We can definitely send a summary = via email. Just to clarify those points you brought up. Syntax highlighting= definitely does exist and is totally discoverable but people still seemed = to miss it. Our best guess as to why so many users miss it is because of th= e relatively small contrast in colors (Navy vs black). Regarding autocomple= te, despite it being documented, almost none of the long time customers we = spoke with knew it existed which suggests they're not reading the docum= entation very closely or at all.

Regarding the com= ments you mentioned, the one regarding column names was talking about prese= rving the column name when moving data to Excel. And I'll admit, the ot= her comment is pretty unclear out of context. We probably should not have i= ncluded it as is.

A summary of the findings will b= e forthcoming.

On Wed, Jan 25, 2017 at 4:25 AM, Dave Page <<= a href=3D"mailto:dpage@pgadmin.org" target=3D"_blank">dpage@pgadmin.org= > wrote:
Hi

On Tue, Jan 24, 2017 at 9:42 PM, Raffi Holzer <rholzer@pivotal.io> wrote:
> Hi,
>=C2=A0 As part of a project to enable pgAdmin4 to work with Greenplum d= atabases,
> we conducted user research into pgAdmin. We wanted to share those insi= ghts
> and potentially develop against them but first wanted to get feedback = from
> the pgAdmin group. To that end we created the video below that summari= zes
> our findings. Let us know what you think.
>
> https://youtu.be/BylcblYw8sU

That's very helpful, thank you. Can you please summarise your fi= ndings
in an email to the list so we can work with it within our normal
process?

I will note that whilst I agree some of the points raised need further
work in pgAdmin 4, some of them make little sense - most notably
Syntax Highlighting which we've had for ~17 years, and works
automatically, thus not requiring any kind of user discovery beyond
typing some SQL into the query tool. Auto-complete is another example
of a feature we've had for years, that is documented. I agree though that there is scope for better discovery mechanisms there.

Some of the other comments highlighted made little to no sense to me,
for example the comment on column names @ ~3:03 and the comment on the
bottom left @ ~3:22 (this is a great example of why email is better
than a video :-) ).

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



--
Raffi Holzer
Product Manager
Pivotal Labs
--001a113f67fcaa709c0546ec2f4e--