Appearance
Sharing Results & Asking for Feedback
Sharing your results and seeking feedback is an integral part of collaborative research. It ensures that your work is moving in the right direction, helps identify potential improvements early, and keeps the entire team aligned.
Why Context Matters
When asking for feedback, it’s important that what you share is contextually complete — meaning anyone reading it should be able to understand your update without needing to ask multiple follow-up questions.
Think of it as if you’re explaining your progress to someone in person: give them the full picture.
What to Include in Your Update
Whenever you share results or ask for feedback, include the following points:
- Problem or Objective: What were you trying to solve or test?
- Results: What did you observe or achieve? Include numerical results, plots, or visualizations.
- Your Observations: What do you think the results indicate? Mention patterns, errors, or interesting findings.
- Feedback Required: Be clear about what you want from others — for example, “Can you check if the boundary setup looks correct?” or “Does this refinement make sense for the next step?”
Adding Visual Context
Visuals make feedback faster and more precise. Always try to include:
- Screenshots or images of your results or setup.
- Short demo videos if they explain the output better.
- Plots or charts when applicable.
Attach these directly in Slack, Obsidian, or your shared workspace so others can easily follow.
Tagging and Communication
When posting your update or question, tag the relevant person or team to ensure they see it promptly. For example:
@Aman – sharing the updated mesh refinement results. Please check if the boundary layer looks consistent before I proceed with the FEniCS run.
Example Post
Update: Completed simulation for the modified patch antenna geometry.
Objective: Validate resonance shift after adjusting substrate height.
Results: Resonant frequency observed at 9.2 GHz (previously 9.4 GHz). Field distribution appears smoother near feed region.
Observation: The change aligns with theoretical expectations, though minor reflection peaks remain.
Feedback Needed: Please review the S11 plot and confirm if the boundary conditions look consistent before proceeding with the next parametric case.
(Attaching field visualization and S11 plot images)
When You Have a Query
Step 1
Spend 15–20 minutes searching for a solution online or using an AI tool like ChatGPT. Copy-paste the error message or issue along with the relevant code. In most cases, this will help you find a quick fix.
Step 2
If the problem remains unresolved, share a screenshot of the error along with the relevant code block and background details. This gives others the context they need to understand and resolve the issue efficiently.
Note: Whenever you share this information, it is highly recommended to also include the response you received in Step 1 (from your online or AI search) and what you tried or implemented based on that response. This helps others avoid repeating suggestions and provides a clearer picture of what has already been attempted.
Step 3
If the issue still persists, schedule a short meeting with the concerned person. Go through the error together, resolve it, and test the fix during the call.
By following this process, we maximize productivity and minimize downtime — keeping communication efficient, structured, and helpful for everyone involved.
Summary
When sharing results or requesting feedback, make your post self-contained, visual, and directed. A complete message — with background, results, observations, visuals, and clear questions — helps others provide accurate and meaningful input, saving everyone time and improving overall project quality.