terminology – Are Product Designers UX Designers who also do Product Management? If not, what’s the diff between the 3?

I’m having to work with Product Managers for the 1st time and we seem to be in a push pull of who does what and who has the final say on this or that. Someone argued that it’s bc I’m a UX Designer rather than a Product Designer. Every time I read an article about the diff between UX and Product design I don’t quite get the difference…

However, if Product Designers take the responsibility of a Product Manager as well, then I understand the difference. Conducting user research, ideation workshops, designing as well as being responsible for the backlog (I don’t mean contributing, I mean responsible for making sure all the ACs are there etc), writing release notes… Having to attend all those meetings with different areas of the business I honestly don’t know how one would have the time to design and do all that. Only in this case I’d say yeah, I’m quite happy with the title of UX Designer!

Mind you: I work on a very complex B2B SaaS product, not a shoe shop… I think that might influence the answers…

terminology – random walk with discrete distribution without replacement

suppose there is a set of vectors $S = { s_1, s_2, cdots, s_n}, s_i in mathbb{R}^2$.

the “random walk” I am interested in is to start at $(0, 0)$,

1, sample a step $s_i$ from $S$ with equal probability.

2, sample second step $s_j$ from $Ssetminus {s_i}$ with equal probability.

3, repeat until all the steps have been enumerated.

Is there any field study on the properties of the trace of this type of “random walk”?

E.g. Expected position within $t$ steps. Convex hull density within $t$ steps.

terminology – Library vs. framework vs API?

A library is a collection of code built to perform common tasks. Library code tends to be relatively stable and bug free. Use of appropriate libraries can reduce the amount of code the need to be written. It will tend to reduce line of code counts for an application will increasing the rate at which functionality is delivered. In most cases, it is better to use a library routine than to write your own code.

An API (Application Programming Interface) is interface to some functionality which allows an application to access the available functionality. An API may be referred to as an Interface. API exist at many levels including system, library, framework, program, and application. APIs should be defined before the code implementing them is implemented.

APIs should be stable, although portions of the API can be deprecated for various reasons. The more broadly used the API the more difficult it is to change it. Most if not all of the Java 1.0 API is still available, although many methods are have been deprecated.

A Framework is a collection of APIs designed to make building of applications simpler. Frameworks provide implementations for reusable components. Good frameworks tend to be specialized in their application.

The Java Collections Framework is a collection of APIs to various types of objects that can be used to handle collections. It provides a hierarchy of APIs to various collections. The in the Java Collections Framework the SortedSet interface extends Set interface which in turn extends the Collection interface. These APIs are abstract interfaces, and the actual implementations have different names. The Collections Framework makes implementing collections simple, and simplifies changing implementations during development.

Frameworks can be built of smaller frameworks as is seen in the Java Spring Framework targeted at J2EE development. Spring consists of over a dozen frameworks, many of which can be used on their own or replaced by other frameworks.

Use of the appropriate libraries, APIs, and frameworks can simplify development. These components take care of the common issues, and allow the development team to focus on the application specific issues.

terminology – Scrolling Behavior – Mobile vs Desktop

We have some internal research that shows our users scroll much further down the page on mobile vs desktop. The page lengths are exactly the same in terms of the amount of products displayed – 3 across and 12 down.

When describing this behavioral difference I call it the ‘Facebook Phenomenon’ as in users just scroll endlessly without fully absorbing the information presented to them.

My question is, is there a UX/analytical term for this behavior? I made up the phrase ‘Facebook Phenomenon’ where I work but wondered if I’d subconsciously copied something I’d read.

terminology – What is a Problem Statement?

Typically Problem Statements are used to define and clarify the problem to be solved in the context of a UX design activity. There are a number of ways to structure or write this, but as long as the problem is written in a simple and clear statement then it is sufficient.

In contrast, a Hypothesis Statement is used to propose an explanation or a suggested solution to a particular question. It is used to help frame the way that the research is carried out, and typically in scientific research one would try to prove the hypothesis to be incorrect so as to avoid certain biases in the methodology and analysis. For example, if your hypothesis is that changing the button colour will improve usability, then you would typically set up some experiments to show that changing the button colour has no effect on usability. And if your data shows that it does have an effect then your hypothesis will have been proven to be valid.

You can define problem statements and hypothesis statements at different levels of detail, depending on the size of the project and the nature of the problems that you are trying to solve. So this can mean one general problem statement for the whole project, and different problems statements for major milestones or challenges to be solved.

Writing user stories is one of the techniques used in agile software development to help with requirements definition. From the Atlassian Playbook:

A user story is an informal, general explanation of a software feature
written from the perspective of the end user. Its purpose is to
articulate how a software feature will provide value to the customer.

Basically it is a good way to help frame the particular design problem from the perspective of the end-user, in terms of the goals that they want to achieve and without prompting what the solution should look like.

terminology – Term “Eye load”?

I am missing a term to describe the mental load which is needed for a human to parse a large menu.

For example I want to switch to google forms:


My eyes need to parse the symbols and/or text to find the right place to click.

I would call it “eye load” but I think this term does not exist.

If you compare this to an autocomplete solution, where a user can enter a text, then an autocomplete solution needs much less “eye load”.

Is there a common UX term for this?

ra.rings and algebras – Representation theory terminology question

For a paper I’m writing, I need a term for a representation-theoretic concept that I’m sure someone has thought of before, so I thought I’d ask here rather than just make something up.

Let $G$ be a group and $R$ be a commutative ring. Consider an $R(G)$-module $V$. For any ideal $I$ of $R$, we have the submodule
$$I V = {text{$c cdot v$ $|$ $c in I$ and $v in V$}}.$$
What is the term for $R(G)$-modules $V$ such that all submodules are of this form? The ones I’m interested in have the additional property that if you ignore the $G$-action, then they are free $R$-modules (though not finitely generated!), but I doubt this matters for this question.

For an easy example, if $R = mathbb{Z}$ and $G = text{GL}(n,mathbb{mathbb{Z}})$, then $mathbb{Z}^n$ has this property.

If $R$ is a field, then this reduces the the usual notion of an irreducible representation, so I think of this as a version of irreducibility. But looking through my ring-theory books, I can’t find it anywhere.

terminology – Is there a common industry term to describe moving a task down in priority to an undefined “later” time?

A note for the moderators: this question is looking for INDUSTRY terminology (like SCRUM, Spike, Big O, Visitor Patter, etc) terminology, not opinions about how I should speak.

Let’s say that in our ticketing system a task will involve doing A, B, C, and D.

While doing the task, I find that doing C will require too large an investment for now and is not very high priority.

I have been saying something like “Let’s do A, B, and D, but I think we should punt on C for now”.

I looked up “punt on” and it seems to mean only to “not do”, not to put off until later. At least that’s what the results in Google told me.

Am I using “punt on” wrong? Is there a better term for this?

terminology – What exactly are “semaphore signal operations” in the Vulkan specification and how do they relate to a CommandBuffer?

In section 7.4.1.Semaphore Signaling of vulkan specification,


“When a batch is submitted to a queue via a queue submission, and it includes semaphores to be signaled, it defines a memory dependency on the batch, and defines semaphore signal operations which set the semaphores to the signaled state.”

What are operations in this sentence?And what is the difference between pipline stages and operations?Is this semaphore signal operation inserted into queue and wait to be executed like stages which a CommandBuffer consists of?

terminology – What is the term for an image sequence with one fixed object in each image?

How is it called if I have movie or image sequence in which one central object is always fixed? For example, the same car in different landscapes, the same kitchen aid in different kitchens, etc.? This is typically used for product marketing movies and I would like to know how this is called. Youtube links, etc., would be appreciated!