Hi there 👋 I’m Julie, Head of Product Design at Product Hunt. AMA 👇

@joris_falter Keep building, keep shipping 💥

@alecdewitz My favorite part is "being in the zone" when you're going with the flow, and things come naturally, and it's exciting and moving fast. For me, the draining/challenging one is the wait between having an idea and having the time and resources to work on it.

@hemantwarier We're currently rebuilding the mobile apps from scratch to be able to add more features on the mobile experience this year. I don't have a precise date for the discussions feature to share at this stage.

@syswarren Also it would be cool if we could integrate launch day upvotes with slack as notifications.

@stanmassueras I judge landing pages on 2 criteria: - Do I understand what the product can do for me in less than 10 seconds? - Is the visual design memorable? If I search for this website again, will I know this is what I was looking for? Bubbles: Video and Screenshot Collaboration Gumroad – Sell what you know and see what sticks Browserless: Headless Automation Lunchbox — Online solutions for enterprise and virtual kitchens

@gabrielnes I only use Figma for personal projects so I can't really answer for this but, we organize files on Sketch in folders in our team workspace. There is a resources folders where you can find templates to start new projects, the components library, datasets... Then, we organize files in different "platforms" folders: Web, Mobile apps, Others. For finished projects, we archive them in another folder to keep some clarity on the active folders. We also name our files with a description of the features or the page that's designed there. So if you're working on something specific, you can search for existing files related to that page/feature for reference, see what was explored before. In the files themselves, we usually have a page for explorations, a page with the final version, and by default, you'll find a page with the different layouts we use for widescreen, desktop, tablet, web mobile. All the symbols/components are fetched from our shared library so it's always up to date.

@kuroumi I'd love to give you a proper answer. Can you provide an example? It'd help!

@syswarren For example, with Product Hunt and thinking of it as a marketplace for consumers to discover and subscribe to/adopt new products, how might PH try to explore and identify new opportunities of expanding its marketplace experience beyond how it works today? Maybe for both creators and consumers?

@kuroumi To answer your initial question: in your first comment, you asked a question with a lot of ambiguity. So my first step was to ask you for an example, and it's exactly how I'd approach a project that's not clear to me. Now, let's use your example: Product Hunt is a marketplace where people can discover products other people share. You're given a project: Expand the marketplace experience. First, you'll want to better define the project by asking questions: "Why does the company want to expand the marketplace experience?" "What does 'expanding the marketplace' mean for the company?" "Can you provide an example?" "Are there long-term goals I'm not aware of that would help direct my explorations?" And then, when you have more definition on the project, you can ask yourself more questions or run a brainstorming session: "What could we do to improve the experience for consumers?" "What could we do to improve the experience for creators?" And because it's a two-way marketplace: "What do consumers need from creators?" "What do creators need from consumers?" "Do we have feedback that would help us answer these questions?" "How can we interview users?" To summarise: - Ask questions to better define the project. If it's not clear, ask for clarification. You're not a mind reader. (At least, I'm not) - Ask questions and work with your team to explore ideas and build agreement. - Ask questions to users to better understand what they need. I hope it helps!

@varsha_sharma1 Sometimes you have to take risks to make an impact. But if you're not completely sure, you can always test the changes to a subset of users, or be prepared to rollback to the previous version.