Matter

Discover your strengths and reach your career aspirations

get it
#4 Product of the DayDecember 05, 2018

Matter is for professionals who want to become the best version of themselves. Discover your strengths, feel amazing at work, and reach your aspirations.

🙌 Thanks for taking the time to learn about Matter.

📣We'd love to hear from you below.

Ready to get started? Visit Matter

Thank you for joining us!

​👨🏾‍🔧​​👩‍🎤​​👨🏼‍🔬​​🧕🏽​​🦹‍♀️🦸‍♂️

Around the web

Reviews

  • Pros: 

    Simple, fast, consistent, and actionable feedback.

    Cons: 

    None.

    Matter has helped me grow exponentially as a designer. Being able to gain feedback without waiting for things like performance reviews has been amazing. I can't wait to see what else their team is able to do with this platform.

    Parker Henderson has used this product for one year.
    Comments (1)
  • Meng To
    Meng ToDesigner
    Pros: 

    Actionable feedback, easy-to-use, great for teams

    Cons: 

    Mobile app?

    Getting constructive feedback on your work is hard within any team environment. Matter solves that by giving you the right tools to get your team on board and share feedback that will help them further their career. I always encourage my team to focus on their skills and growth, so Matter is a unique and effortless way to provide the necessary guidance to achieve that.

    Meng To has used this product for one day.
    Comments (2)

Discussion

You need to become a Contributor to join the discussion - Find out how.
Brett Hellman
Brett HellmanMakerPro@bretthellman · ceo@matter • former ceo@hall (acquired)
Hey PH 👋🎉 After a year in closed beta, we’re excited to open up Matter to everyone. We believe: 🏆 Peer feedback is the silver bullet to reaching your aspirations. 👩‍🔬 People perform better when they hear monthly peer feedback (proven by science too!). 🧙‍♂️ Everyone deserves the opportunity to achieve mastery, learn, grow, and be respected by their peers. ✨ Matter makes feedback easier, pleasant, and more productive. ✨ How do we know? Because our customers told us! "The app is amazing. Everything about it, from the interface to the way in which I am able to send and receive feedback is amazing." - Product Manager at Dribbble "Matter is an empathetic experience which directly speaks to your heart, connecting yourself to your peers and driving betterment." - Designer at Adobe "As knowledge workers, we are paid to use our brains. We spend too little time improving how our brains work. Matter is an incredibly powerful way to grow your skills." - Product Leader at Airbnb 💬 If you have any questions, just reply — the team is around all day! Thank you for joining us! 👩🏻‍🎨👨🏾‍🔧​​👩‍🎤​​👨🏼‍🔬​​🧕🏽​​🐼 P.S.: A special thanks to: @mechanical_turk for being employee #1. @jw for all his design genius. @marcreisen for joining me for another startup adventure. Brian Brasher for his amazing skill badge illustrations. My Mom! I couldn’t have done anything w/o her.
marc reisen
marc reisenMaker@marcreisen · Designer
👋Product Hunt 😻 As @bretthellman mentioned this is our second go at doing a StartUp together. When Brett shared the idea around Matter with me well over a year ago, and here we are! One of the reasons I left my role at Atlassian as the Design Manager of Bitbucket, and joined Matter is that I am passionate about personal betterment, growth and improvement. The truth is our current state, is not always the best version of ourselves that we can be. It takes change, new challenges, experiences and even failure. This helps us recognize the things we need to improve, foster and in some cases even forget. As a manager, there are several opportunities for us to learn and discover our blindspots. From our peers, team members and our managers/manager. I've spent my time working and focusing on Product and Design. Creating, iterating, crafting. We've managed to balance fun and engaging experiences on Matter that help our users feel empowered and enabled to go out and receive amazing feedback from the people we work with. We've got a lot of exciting ideas and an incredible 🔮vision for Matter and it's future. Please feel free to reach out and ask and Product or Design related questions. Our Toolset 🛠🎨 • Figma • Adobe XD and Creative Cloud Matter is on a mission to improve not only how we engage with feedback, but equally how we learn to give and receive it. We believe: Everyone is deserving of Respect and feeling Accepted ✌️ We all have a desire to learn and grow 🌱 Feedback is a fundamental component to personal growth and betterment 🎯 Why? Because who you are right now, is not the best version you, YOU can be. 💜
Brett Hellman
Brett HellmanMakerPro@bretthellman · ceo@matter • former ceo@hall (acquired)
@marcreisen yea! we're live 💡 nothing like a little public team PDA. And a special thanks to @jw for introducing us to @Figma ... @zoink
Parker Henderson
Parker Henderson@parkerhendo · Designer
Hey @bretthellman @marcreisen and @mechanical_turk! I'd love to hear more about how you all are using Figma and its benefits when working in a small team, especially for handoffs between design and engineering. We currently use it at my company and it definitely has it's pros/cons and requires a different approach compared to workflows like Sketch + Abstract, so I'd love to hear your take on it.
Kerem Kazan
Kerem KazanMaker@mechanical_turk · Founding Engineer @Matter
@parkerhendo The engineering experience on Figma has been really nice to be honest. As a simple engineer who doesn't have a background in product or design, I find it really helpful to see exactly what I need to build. Usually what happens is our founder @bretthellman teams up with our design lead @marcreisen to create a concept. Then marc takes over and starts his design iterations. Over the course of a few days, a feature gets ironed out through non-stop feedback. Finally, marc adds the polish and makes it beautiful. We'll usually have read access to the documents from the beginning of the ideation phase. This makes it easier to develop the feature as a team. Once marc showcases the final designs, we take them over and start building. 80% of the feature is really easy to follow from Figma. I usually never have to bother marc. For the remaining 20% though, while building the designs, new issues arise inevitably. We usually discuss them on person or via Slack. The end result usually sticks about 95% true to the designs on figma. Overall, as a read-only engineer user of Figma, I'll say that it makes my job easier for sure. It's a really good product.
Brett Hellman
Brett HellmanMakerPro@bretthellman · ceo@matter • former ceo@hall (acquired)
@marcreisen @mechanical_turk @parkerhendo I feel like FIGMA should be paying me at this point 😜 In terms of how we used @Figma to create Matter, the only thing I could add is the value of using their commenting tool. It's a nice way to collaborate around feedback while keeping track of what is open/closed. It's also nice having the commenting inline with document vs outside of the design on a @trello board.
Parker Henderson
Parker Henderson@parkerhendo · Designer
@marcreisen @mechanical_turk @figma @trello @bretthellman Commenting is definitely one of my favorite features in Figma, even for adding personal notes on thoughts through my designs!
Jonathan Simcoe
Jonathan Simcoe@jdsimcoe · Futurist, with reservations. //////\
Matter is an incredible product! I've had the pleasure of chatting with @bretthellman about Matter during the closed beta and it has helped me at a pivotal point in my career to get really valuable feedback. Everyone needs ways to be built up and grow—as professionals and human beings.
Brett Hellman
Brett HellmanMakerPro@bretthellman · ceo@matter • former ceo@hall (acquired)
@jdsimcoe love hearing this story! I'm glad you like it. I hope you'll continue to use Matter as your career progresses ❤️
Kerem Kazan
Kerem KazanMaker@mechanical_turk · Founding Engineer @Matter
Hi everyone! This is Kerem Kazan ( @MechanicalKazan), founding engineer @Matter_HQ. I’m here to shed some light on questions coming from the engineers among you. Here's a brief overview of how we built Matter: Matter is a web app, written in NodeJS. For about 50% of our app, we use ES6 and compile it down via Babel. The more recent parts of our app is written in TypeScript, and we are in the process of migrating the rest to TypeScript as well. We also depend heavily on eslint & tslint for a consistent code style. We have a fairly large code base, with 9 standalone packages that together comprise Matter. We use yarn workspaces to orchestrate how these packages depend on each other. If I had to break down our app into its most fundamental parts, we’d have 4 sections: a) @matterapp/matter-ui: Our frontend component library. Written in React, developed with Storybook. We use styled-components along with grid-styled to manage our css. b) @matterapp/web-client: Our web app’s frontend code. At its core, it’s a create-react-app project. It combines and composes the components in @matterapp/matter-ui. We use Redux for local state management, and Redux-form for our forms. We use Recompose for maintaining our higher order components. Also, ReactRouter for client-side routing. For remote state management, we use apollo-client. All of our user-facing api is written in GraphQL, (and yes, it’s been amazing). We use CypressJS for automated end-to-end testing of our entire app. c) @matterapp/graphql-server: Our web app’s user facing api server. At the bottom of the stack, we have Koa. Our Koa server connects to our MariaDB sql database via KnexJS & Objection. We’re in the process of picking another ORM, (something more typescript friendly). We’ll either go with TypeORM or Sequelize-Typescript. Our server has one endpoint for user-facing api calls, and that’s our GraphQL endpoint. Because Matter needs a bunch of 3rd party integrations, we also use Grant for OAuth solutions. Authentication is handled via the beloved jsonwebtoken library. d) @matterapp/lambdas: Our background jobs system. We use serverless-framework to interface with aws. This coebase is written purely in TypeScript. The users never directly invoke calls on this part of our stack. This is strictly for background jobs like batch processes or cron jobs. Usually, our graphql-server puts something to an SQS queue, and the lambdas pick it up. Sometimes the graphql-server sends direct api-calls via api-gateway. We use inversify-js on our lambdas for inversion of control. So, there you have it :) A brief overview of Matter’s tech stack. Let us know what you think. Feel free to give some feedback, ask questions, or provide criticism. Looking forward to learning from you!
Brett Hellman
Brett HellmanMakerPro@bretthellman · ceo@matter • former ceo@hall (acquired)
@philmil22637493 🤔 great question. I defer to Kerem to share why Cypress specifically. I will say from a product leader perspective, @cypress_io has been lightyears better than my previous experiences w Selenium. If you love JavaScript you should try it out. OK, back to promoting my own product now 😜
Kerem Kazan
Kerem KazanMaker@mechanical_turk · Founding Engineer @Matter
@philmil22637493 cypress is a relatively new player in the end-to-end testing arena. however, they are surprisingly robust, and very responsive. Every now and then, we run into issues with their library, but they are almost never slow to respond. I think they secured a big funding recently as well. Give them a shot, it's been really nice for us.
Parker Henderson
Parker Henderson@parkerhendo · Designer
@mechanicalkazan @matter_hq @matterapp @mechanical_turk What was your reasoning for switching to Typescript? I've been trying it myself, but I feel like it slows me down quite a bit in comparison to vanilla ES6.
Kerem Kazan
Kerem KazanMaker@mechanical_turk · Founding Engineer @Matter
@parkerhendo in my opinion, for early prototypes and small projects, using vanilla JS is the way to go. that's actually what we did here at Matter. So I would agree with your comment that it slows you down. However, we found that there was a good point over the lifespan of a software project where that slowdown is actually worth it. The value of strongly-typed languages, such as TypeScript, comes right around when a project stops being a small prototype, and the number of people working on it starts to increase. A really high percentage of software bugs (I believe about 80%, but dont quote me on this) come from type errors. A strongly typed language can catch those errors at compile time, which will immediately eliminate a huge pain point, just like that. The tradeoff here, is that you have an initial fixed cost when you are establishing your type system. However, that small investment pays big time over the lifespan of a project. In fact, having types, combined with smart editors that auto-complete your code via suggestions, will definitely make it faster to develop over time. Finally, types address one of the biggest coding problems: communicating developer intent. A smart and concise type name can help a team of developers quickly understand what they are working on. When we stop coding solo, and start collaborating with others, programming becomes a whole different game. At that point, anything that makes communication easier is worth a try. Hope you find this useful @parkerhendo. Thanks so much for asking these really intriguing & engaging questions. I honestly really appreciate your involvement both here and on twitter. Please let me know if I can help answer any other questions. All the best
Kenneth Kel
Kenneth Kel@kenneth_kel
Hello everyone, I am a research scientist at UC Berkeley’s psychology department and I happen to be in a team with two bosses who dislike one another. I was at Wharton before Berkeley and something called a “360 feedback” was the tool we used to alleviate tension between team members. In essence, every person grills every other person in the team until everyone is finished. After several weeks of asking my superiors to do a “360”, I realized that while face-to-face hostility is customary amongst business folk, academics are on the softer end of the spectrum and tend to avoid real life confrontation. I guess this explains why we publish papers as opposed to hosting debates on live TV 😂 Googling for a solution I came across the Matter app and to my astonishment I received written feedback from my superiors the night I submitted mine. This was so unexpected that I decided to look it up and it turns out that while written feedback is as effective as spoken, written is much easier to give (https://doi.org/10.1089/10949310... and https://scholarworks.wmich.edu/m...). We might need many more exchanges on Matter to resolve all our problems but our team dynamics have become much healthier. This platform is a useful tool and I wish the best of luck to the Matter team! Cheers, Kenneth
Brett Hellman
Brett HellmanMakerPro@bretthellman · ceo@matter • former ceo@hall (acquired)
@kenneth_kel this is amazing! We are so happy you found Matter and are having a great experience using Matter to receive feedback and grow. We're lucky to have you as one of our early users. Thank you!
Danielle Roubinov
Danielle Roubinov@droubinov · Danielle; psychologist at UCSF
@kenneth_kel Hi Kenneth! As a fellow psychologist in academia, I applaud (and very much agree with!) this comment. In graduate school, there was no formal mechanism or structure for receiving feedback and I really wish there was. Other academic settings are similarly noncommittal and it does such a disservice to professionals in this field. Giving/receiving regular feedback paves the way for individual and team growth. Would love to see this kind of thing adopted more broadly in our field!